n8n workflow templates
Ready-made n8n workflows over the FilingPulse API: SEC filing notifications in Slack, Discord, email, or anything else n8n connects to. Import a template, paste a free API key, activate. Each template is a plain n8n workflow JSON — no community node install required.
The templates
| template | what it does | trigger |
|---|---|---|
| insider-alerts-webhook | Real-time Form 4 insider trade alerts, pushed by FilingPulse's HMAC-signed webhooks seconds after a filing lands. Server-side ticker filters. Verifies the signature before trusting anything. | FilingPulse webhook (push) |
| insider-alerts-polling | Same alerts by polling every 10 minutes — no public URL needed, so it works on a laptop or behind NAT. Remembers seen filings; the first run seeds quietly instead of flooding. | Schedule (10 min) |
| 8k-daily-digest | One message a day summarizing the last 24 h of 8-K corporate events — counts by SEC item number (2.02 earnings, 5.02 officer changes, …) plus a sample of filings. | Schedule (daily) |
How to import
- In n8n: Workflows → Create Workflow → ⋯ menu → Import from URL… and paste the template link above (or download the JSON and use Import from File…).
- Follow the yellow setup note inside the workflow — each template documents its own
2–5 minute setup (API key, Slack/Discord webhook URL, and for the push template the
subscription
curl). - Activate. Free tier needs no card; see the API docs for quotas and the full endpoint surface.
Webhook signature verification
The push template verifies X-FilingPulse-Signature: sha256=HMAC_SHA256(secret,
raw_body) in a Code node before trusting a delivery — anyone can POST to a public
n8n webhook URL, so don't skip this. The subscription secret is returned once by
POST /v1/webhooks. On self-hosted n8n instances that block built-in modules
in Code nodes, set NODE_FUNCTION_ALLOW_BUILTIN=crypto. Details:
webhook docs.
Beyond Slack
The last node in each template is a plain HTTP Request pointed at a Slack
incoming-webhook URL. Swap it for any n8n node — Discord (change the JSON body to
{"content": …}), email, Telegram, Google Sheets, a database write — the
formatted alert text arrives as {{ $json.text }}.
Prefer code over workflows? The same alerts are a few lines with the Python or JS SDK, and agents can use the hosted MCP server directly.