n8n Twitter webhook for account monitor hits
Point an XFlux monitor at your n8n Webhook node. On Starter+, each matching tweet POSTs a signed monitor.hit payload you can branch into any n8n workflow.
Webhook node as the entry
Create an n8n Webhook trigger, copy the production URL into XFlux, then Test.
Verify signatures in the flow
Use a Function/Code node to check X-XFlux-Signature before trusting the body.
Same pattern as Make.com
If your team already uses Make, see /docs/integrations/make — concepts transfer cleanly to n8n.
n8n wiring
- 1
Add Webhook trigger in n8n
Method POST, path of your choice. Activate the workflow to get a public HTTPS URL.
- 2
Save URL on the XFlux monitor
Rotate secret if needed. Store the signing secret in n8n credentials/env.
- 3
Branch on event === monitor.hit
Map tweet.text / authorUsername into Slack, Telegram, Sheets, or your DB.
HMAC check sketch (n8n Code node)
Reject requests that fail signature or stale timestamps. Full details in webhook docs.
// Pseudocode inside n8n Code node
const crypto = require("crypto");
const raw = $input.first().json.rawBody; // capture raw body
const ts = $input.first().headers["x-xflux-timestamp"];
const sig = $input.first().headers["x-xflux-signature"];
const expected =
"sha256=" +
crypto.createHmac("sha256", process.env.XFLUX_WEBHOOK_SECRET)
.update(`${ts}.${raw}`)
.digest("hex");
if (sig !== expected) throw new Error("bad signature");FAQ
- Does XFlux have a native n8n node?
- Not required — standard Webhook trigger works. A dedicated node may come later; signed HTTP is enough today.
- Free plan live delivery?
- Free supports Test webhooks. Live hits need Starter+. You can still prototype the n8n graph with Test events.
- Make.com vs n8n?
- Same XFlux event. Choose based on your automation stack — Make guide is already documented.
Related guides
Try account monitors free
Free includes 1 monitor and Dashboard hit history. Live webhook delivery starts on Starter ($19/mo).