Connect Twigest to Any Service
Power users and developers can push Twigest digest data to any destination. Build custom automations, feed your data warehouse, or trigger workflows in n8n, Make, or your own backend.
- ✓JSON payload posted to any HTTPS endpoint when digest is ready
- ✓Includes raw tweets plus AI classifications and sentiment
- ✓Retry-on-failure with exponential backoff (5 attempts)
- ✓HMAC-SHA256 signature header for authentication
- ✓Available on Business plan and above
What you get
Connect to Any Endpoint
POST digest data to any URL — your own backend, n8n, Make (Integromat), Airtable, a data warehouse, or a custom application.
Structured JSON Payload
Every webhook delivers a clean JSON object with the digest summary, top tweets, keyword volumes, and metadata — ready to parse and store.
HMAC Signature Verification
Every request includes an HMAC-SHA256 signature so you can verify it genuinely came from Twigest — no spoofing possible.
Automatic Retry Logic
If your endpoint is temporarily unavailable, Twigest retries with exponential backoff — so no digest is ever silently lost.
Sample payload
Every webhook POST includes a structured JSON body. Here is an example of what your endpoint receives when a digest is created:
{
"event": "digest.created",
"digest_id": "dgst_abc123",
"account": "@yourhandle",
"keyword": "brand mention",
"generated_at": "2026-03-18T08:00:00Z",
"summary": "AI-generated summary...",
"tweet_count": 42,
"top_tweets": [ ... ],
"sentiment": "positive"
}Set up in 4 steps
Upgrade to Business Plan
Webhooks require Business plan or above for security and rate-limit handling. Upgrade from your account settings.
Add Your Endpoint URL
Go to Dashboard, open Channels, click Add Webhook, and paste your HTTPS endpoint URL.
Copy Your HMAC Signing Secret
Twigest generates a unique signing secret. Copy it and use it in your endpoint to verify every incoming payload.
Verify the Test Payload
Click Send Test to fire a sample payload. Confirm your endpoint receives it and validates the HMAC-SHA256 signature correctly.
Frequently asked questions
What does the payload look like?+
Each POST body is a JSON object containing the event type (digest.created), digest ID, the monitored account or keyword, an AI-generated summary, tweet count, an array of top tweets with text and engagement data, and a sentiment field. See the sample payload below for the exact shape.
How is the webhook secured?+
Twigest signs every request with HMAC-SHA256 using a secret you copy from the dashboard. The signature is sent in the X-Twigest-Signature header. Compute the HMAC of the raw request body with your secret and compare it to reject spoofed requests.
What is the retry policy?+
If your endpoint returns anything other than a 2xx status, Twigest retries up to 5 times using exponential backoff starting at 30 seconds. After 5 failed attempts the delivery is marked as failed and you receive a Telegram or email alert depending on your notification settings.
Can I filter what triggers the webhook?+
Yes. When adding a webhook channel you can scope it to specific accounts, keywords, or event types. For example, you can configure one endpoint to receive only spike-alert events and another to receive all digest.created events.
What plan includes webhooks?+
Webhooks are available on the Business plan and above. The Business plan also includes higher rate limits and priority delivery to ensure your endpoint receives payloads within seconds of digest generation.
Build your custom Twitter data pipeline
Webhooks are available on Business plan and above. Start free, upgrade when you need custom integrations.