Connect XFlux to Make.com

Use XFlux account monitors to watch public @handles on a schedule. When a new tweet matches your filters, XFlux POSTs signed JSON to your endpoint — no polling code on your side. This guide wires that into a Make.com Custom Webhook so you can route alerts to Slack, Telegram, Google Sheets, or any API Make supports.

Works the same way with Zapier (Webhooks by Zapier) and n8n (Webhook node). Replace the Make steps with their webhook trigger.

What you will build

@elonmusk posts a new tweet (optional keyword filter)
        ↓
XFlux monitor detects hit (1s–5min poll, plan-dependent)
        ↓
Signed HTTP POST → Make Custom Webhook URL
        ↓
Make scenario: filter → Slack / Telegram / Sheets / HTTP module

1. Create a Make Custom Webhook

1. Log in to Make.com and create a new Scenario.
2. Add the first module: Webhooks → Custom webhook.
3. Choose Add to create a new webhook. Make shows a unique URL like https://hook.us2.make.com/xxxxxxxx.
4. Copy that URL — you will paste it into XFlux in the next step.
5. Leave the scenario in Instant or scheduling mode as you prefer; turn the scenario ON before testing.

2. Add a monitor in XFlux

1. Create a free XFlux account if you do not have one.
2. Dashboard → Monitors → create a monitor for a public @username.
3. Optional: add keywords (comma-separated). A hit requires the tweet text to contain at least one keyword. Leave empty to alert on every new tweet from that account.
4. Set check interval (Starter+ supports 1s minimum).
5. Expand the Webhook section → paste your Make URL → Save.
6. Copy the signing secret shown once and store it securely (optional for Make, required if you add a verification step later).

3. Send a test webhook

In the monitor Webhook panel, click Test webhook. Make should receive a POST with event: monitor.test. In Make, open the webhook module execution history to confirm a 200 response.

{
  "event": "monitor.test",
  "monitor": {
    "id": "clx...",
    "targetUsername": "elonmusk",
    "keywords": "launch, token"
  },
  "test": true
}

4. Live hits from Make

On Starter+, when a new tweet passes your keyword filter, XFlux POSTs:

{
  "event": "monitor.hit",
  "monitor": {
    "id": "clx...",
    "targetUsername": "blknoiz06",
    "keywords": "launch, CA, pump.fun"
  },
  "tweet": {
    "id": "1234567890",
    "text": "New token launch on Solana ...",
    "authorUsername": "blknoiz06",
    "createdAt": "2026-09-10T12:00:00.000Z"
  },
  "detectedAt": "2026-09-10T12:00:05.000Z"
}

In Make, map fields from the webhook body into downstream modules — for example tweet.text, tweet.authorUsername, detectedAt.

5. Example Make follow-ups

• Router — branch on event (monitor.test vs monitor.hit) or keyword matches in tweet.text
• Telegram / Slack — send a formatted alert with tweet text and link https://x.com/{authorUsername}/status/{tweet.id}
• Google Sheets — append a row per hit for logging or manual review
• HTTP — forward parsed fields to your trading bot or internal API

Headers & verification

Each delivery includes signed headers. Make ignores them by default; for custom verification middleware, see the full webhook reference.

Content-Type: application/json
X-XFlux-Event: monitor.hit
X-XFlux-Timestamp: 1710000000
X-XFlux-Signature: sha256=<hex>
User-Agent: XFlux-Webhook/1.0

Troubleshooting

• Test returns 400 in Make — scenario may be off, or the webhook module expects a different structure. Re-run Test after turning the scenario ON.
• Test works, no live hits — keywords may be too strict, or the account has not posted since the monitor baseline. Try clearing keywords temporarily or use Dashboard → Check now.
• Free plan — live hit delivery requires Starter+. Test pings work on Free to validate the Make URL.