Twigest
zapierautomationtwitter monitoringwebhooksno-codehow-tointegrations

How to Set Up Zapier Automation with Twitter Monitoring (Step-by-Step)

Twigest Team

What You'll Build

By the end of this guide, you'll have a working Zapier automation that:

  1. Receives a webhook from Twigest every time a new AI digest is generated
  2. Formats the summary inside Zapier
  3. Posts the digest to a Slack channel automatically

The same pattern applies to any other app in Zapier's library — HubSpot, Notion, Google Sheets, Salesforce — swap the final action and you're done.

Time required: 10 minutes

Requirements: A Twigest Pro or Business account + a free Zapier account


Step 1: Create a Zap with a Webhook Trigger

  1. Log in to Zapier and click + Create Zap
  2. In the trigger search box, type Webhooks by Zapier and select it
  3. Choose Catch Hook as the trigger event
  4. Click Continue — Zapier will generate a unique webhook URL like:

```

https://hooks.zapier.com/hooks/catch/1234567/abcdefg/

```

Copy this URL. You'll paste it into Twigest in the next step.


Step 2: Configure the Webhook in Twigest

  1. Log in to your Twigest dashboard
  2. Go to Settings → Webhooks in the left sidebar
  3. Click Add Webhook Endpoint
  4. Paste your Zapier webhook URL into the Endpoint URL field
  5. Under Events, check the events you want to receive:

- digest.created — triggers when a new AI digest is ready

- spike.detected — triggers when unusual volume is detected on a keyword

- lead.found — triggers when a tweet with purchase intent is detected

  1. Click Save

Twigest automatically generates an HMAC signing secret and displays it. Save this — you can use it in Zapier to verify that requests genuinely come from Twigest.

Test the Connection

Click Send Test Payload next to your new endpoint. Twigest sends a sample digest.created event to your Zapier URL immediately. Switch back to Zapier — you should see "We found a request!" appear on screen.

Click Continue with found data to move on.


Step 3: Inspect the Webhook Payload

When Zapier catches the test payload, it parses all the fields automatically. For a digest.created event, you'll see fields like:

FieldDescription
eventdigest.created
keywordThe tracked keyword that triggered the digest
summaryThe AI-generated summary text
sentiment_scoreOverall sentiment (-1 to 1)
dominant_emotionjoy, anger, fear, surprise, neutral
top_tweetsArray of the most relevant tweets
period_start / period_endDate range covered by this digest
created_atTimestamp of digest generation

These field names are what you'll use in subsequent Zapier steps to build your message.


Step 4: Add the Slack Action

Now add the destination step.

  1. Click the + button below the trigger to add an action
  2. Search for Slack and select it
  3. Choose Send Channel Message as the action event
  4. Connect your Slack account if you haven't already
  5. Configure the message:

Channel: #brand-monitoring (or whichever channel you prefer)

Message Text — click inside the field and use Zapier's data pills to build a formatted message:

```

📊 New Digest: {{keyword}}

{{summary}}

Sentiment: {{sentiment_score}}Emotion: {{dominant_emotion}}

Period: {{period_start}} → {{period_end}}

```

Replace {{keyword}}, {{summary}}, etc. with the actual data pills from the webhook payload (they appear as blue chips when you click the field).

  1. Click Continue, then Test action — your message should appear in Slack within seconds

Step 5: Turn On the Zap

  1. Review your Zap: Webhook trigger → Slack action
  2. Click Publish (top right)
  3. Toggle the Zap On

That's it. Every time Twigest generates a digest for one of your tracked keywords, Zapier automatically posts it to Slack. No dashboards to check, no manual copy-pasting.


Variations: Other Automation Ideas

The same setup works for any Zapier action. Here are three more common patterns:

Leads → HubSpot CRM

Trigger: lead.found

Action: HubSpot → Create Contact

Map the fields:

  • Contact email → leave blank (or extract from author_url if available)
  • Notes → tweet_text + intent_type + tweet_url

Potential customers are captured in your CRM the moment they signal buying intent on Twitter.

Digest → Notion Database

Trigger: digest.created

Action: Notion → Create Database Item

Map the fields:

  • Name → keyword + created_at
  • Summary → summary
  • Sentiment → sentiment_score
  • Tags → dominant_emotion

Build a searchable archive of all your Twitter intelligence, automatically organized in Notion.

Spike → Google Sheets Log

Trigger: spike.detected

Action: Google Sheets → Append Row

Columns: keyword, current_volume, baseline_volume, spike_percentage, detected_at

Track every volume anomaly in a spreadsheet for later analysis.


Verifying Webhook Signatures (Optional but Recommended)

If you add a Code by Zapier step before your action, you can verify the HMAC signature to ensure the webhook genuinely came from Twigest.

Every Twigest webhook includes two headers:

```

X-Twigest-Event: digest.created

X-Twigest-Signature: sha256=<hmac_hash>

```

To verify in a Zapier Code step (JavaScript):

```javascript

const crypto = require('crypto');

const secret = 'your_signing_secret_here';

const signature = inputData.twigest_signature; // from webhook header

const body = inputData.raw_body;

const expected = 'sha256=' + crypto

.createHmac('sha256', secret)

.update(body)

.digest('hex');

output = [{ valid: crypto.timingSafeEqual(

Buffer.from(signature),

Buffer.from(expected)

)}];

```

If valid is false, add a Filter by Zapier step to stop the Zap from running on invalid requests.


Troubleshooting

Zapier says "No new data found" when testing

→ Go back to Twigest → Webhooks and click Send Test Payload again. Make sure the webhook status shows as "Active."

I see the test but live events aren't coming through

→ Check that the Zap is turned On (green toggle). Free Zapier accounts only run Zaps every 15 minutes — upgrade to Starter if you need real-time delivery.

The `summary` field is empty

→ This can happen if the digest was generated before your keyword had enough data. Twigest digests require at least 5 matching tweets in the period. Wait for the next digest cycle.

I want to filter by keyword

→ Add a Filter by Zapier step immediately after the trigger. Set the condition: keyword contains your_keyword_name. This lets you run different Zaps for different keywords.


What's Next

Once you have the basics working, explore more advanced setups:

  • Multi-step Zaps: Send to Slack AND log to Notion in a single Zap
  • Filters: Only notify on digests with sentiment_score below -0.5 (negative sentiment alerts)
  • Formatter: Use Zapier's Formatter step to truncate long summaries or reformat dates
  • Make (formerly Integromat): Prefer more visual flows? The same webhook URL works in Make — see our full webhooks guide for a comparison

Get Started

  1. Sign up for Twigest — webhooks are available on Pro and Business plans
  2. Add 2–3 keywords you want to monitor (brand name, competitor, industry term)
  3. Follow this guide to connect Zapier
  4. Your first automated digest will arrive within 24 hours

Stop checking dashboards. Let Twigest push insights directly to the tools your team already uses.


Related reading:

Ready to get started?

Join thousands of creators and researchers who use Twigest to monitor X intelligently.

Get Started Free

Get social media tips in your inbox

Join 2,000+ marketers and researchers who get our weekly newsletter on X/Twitter monitoring, AI tools, and growth strategies.