How to Send Trending Topics to Zapier with Webhooks

To push live trending topics into Zapier, configure a Catch Hook (or Catch Raw Hook) trigger so an external platform can POST JSON payloads to a unique hooks.zapier.com URL and start multi-step Zaps. TrendsAGI supports this path with signed outbound webhooks for trend and alert events; there is no native Zapier app, so the connection uses webhooks or the REST API as documented by Zapier Help and zapier.com.

This guide walks through creating the Zapier Catch Hook, mapping a structured trend payload (velocity, growth, summary, themes, sentiment), testing with curl or Python, handling signatures and arrays, and common downstream actions such as Google Sheets or Slack. It stays within the verified Webhooks by Zapier behavior and the TrendsAGI delivery options (signed webhooks, Slack notifications, Google Sheets exports, REST API).

What you need before starting

You need a Zapier account that can use Webhooks by Zapier and a TrendsAGI account that can emit signed outbound webhooks for trend or alert events. Webhooks by Zapier is described by Zapier as a premium feature used to receive instant POST, PUT, or GET data via Catch Hook or Catch Raw Hook triggers that generate unique URLs. Downstream steps can log data to Google Sheets or notify Slack, among the more than 9,000 apps Zapier connects.

TrendsAGI measures velocity as a measured snapshot rate (posts per hour from stored snapshots), not a forecast or unique-user count. Recommendation confidence measures evidence completeness. Use only the REST API base URL https://api.trendsagi.com with header X-API-Key or Authorization: Bearer, or the Python SDK, when you need to fetch or enrich data outside the webhook path.

Step 1: Create a Catch Hook URL in Zapier

According to the Zapier Help article “Trigger Zap workflows from webhooks,” open the Zap editor, choose Webhooks by Zapier as the trigger, and select Catch Hook (parsed body) or Catch Raw Hook (unparsed body up to 2 MB plus headers). Continue, then copy the unique URL that appears (format similar to hooks.zapier.com/hooks/catch/...).

Catch Hook is the usual choice for clean field mapping. Catch Raw Hook is useful when you need the original body and headers for signature checks. In Team and Enterprise accounts, changing Zap ownership changes the Catch Hook URL; update the destination in TrendsAGI if that occurs.

Step 2: Understand the trend payload shape

Send a single JSON object or an array of objects so Zapier can parse fields for later steps. A practical single-event shape that aligns with TrendsAGI trend data looks like this:

{
  "event_type": "trend_alert",
  "trend_id": 12345,
  "name": "AI chip supply",
  "category": "Technology",
  "velocity": 420,
  "growth": 0.37,
  "volume": 18500,
  "summary": "Rising discussion around manufacturing capacity and export controls.",
  "key_themes": ["semiconductors", "export controls", "capacity"],
  "sentiment": "mixed",
  "audience": "tech analysts, policy watchers",
  "marketing_angles": ["B2B thought leadership", "paid social around supply chain"],
  "timestamp": "2026-10-13T19:30:00Z"
}

Velocity is a measured snapshot rate. Keep payloads compact; Zapier documents a 10 MB limit for trigger payloads and 2 MB for Catch Raw Hook. Prefer one event per request or a short array rather than large nested documents.

Step 3: Configure the signed webhook in TrendsAGI

In TrendsAGI, register the Zapier Catch Hook URL as the destination for signed outbound webhooks for trend and alert events. The platform signs the requests so receivers can verify authenticity. When you need headers for verification, use Catch Raw Hook in Zapier; the standard Catch Hook focuses on the parsed body.

If you also want scheduled or on-demand pulls, use the REST API or Python SDK in parallel. Example SDK usage to inspect current high-velocity trends before deciding what to alert on:

import os
from trendsagi import TrendsAGIClient

client = TrendsAGIClient(api_key=os.environ["TRENDSAGI_API_KEY"])
trends = client.get_trends(category="Technology", sort_by="velocity", limit=5)
for t in trends.get("trends", []):
    print(t["id"], t["name"], t.get("velocity"))

For a one-off test POST to your Zapier URL from any machine that can reach the internet:

curl -X POST "https://hooks.zapier.com/hooks/catch/YOUR_ID/YOUR_KEY/" \
  -H "Content-Type: application/json" \
  -d '{
    "event_type": "trend_alert",
    "trend_id": 12345,
    "name": "AI chip supply",
    "category": "Technology",
    "velocity": 420,
    "growth": 0.37,
    "volume": 18500,
    "summary": "Rising discussion around manufacturing capacity and export controls.",
    "key_themes": ["semiconductors", "export controls", "capacity"],
    "sentiment": "mixed",
    "timestamp": "2026-10-13T19:30:00Z"
  }'

Step 4: Map fields and add actions

After Zapier receives a test payload, map the parsed fields (name, velocity, summary, key_themes, etc.) into action steps. Common patterns:

• Create or update a row in Google Sheets with trend name, velocity, growth, and timestamp.
• Post a formatted message to Slack containing the summary and marketing angles.
• Create a task or page in a project tool with the trend ID and a link back to the TrendsAGI trend detail.

TrendsAGI also offers direct Slack notifications and Google Sheets exports; use those when you do not need the full Zapier multi-app routing. Ad-platform connectors (Google Ads, Meta Ads and Conversions API, TikTok Ads, LinkedIn Ads, Microsoft Ads, Pinterest Ads, Snapchat Ads, Reddit Ads) preview changes before explicit execution and are separate from the Zapier path.

Step 5: Handle arrays, signatures, and volume

If the sender posts an array of trends, Zapier can treat the items as line items depending on how the payload is structured; test with a small array first. For signature verification, prefer Catch Raw Hook so headers are available, then add a Code by Zapier or filter step if you need custom checks. Exact signature header names and algorithms are defined by the sending platform’s webhook contract; treat them as opaque until you confirm the values in a raw capture.

Zapier documents rate limits for Webhooks by Zapier of 20,000 requests every 5 minutes per user (and 1,000 per Zap for certain legacy routes). High activity may return 200 while delaying processing; implement retries with exponential backoff on the sender side. Payload size limits are 10 MB for triggers and 2 MB for Catch Raw Hook.

Practical use cases

• Marketing or growth teams: route high-velocity trends into a Slack channel and a Google Sheet for daily review, then trigger paid-media checks only when growth exceeds a threshold.
• Newsrooms and PR: capture crisis-related trend alerts (via TrendsAGI crisis events or watchlist alerts) into a shared sheet and notify the on-call channel.
• Creators and operations: log emerging topics with AI-generated summary and audience notes so content calendars stay current without constant manual scanning.
• Developers building agents: combine the webhook trigger with TrendsAGI agent tools (list_trends, get_trend_ai_insights, list_recommendations) when an agent needs both push events and pull enrichment.

Troubleshooting

If the Zap does not fire, confirm the Catch Hook URL matches exactly, the Zap is turned on, and the payload is valid JSON, form-encoded, or XML. Invalid payloads may still receive a success response from Zapier while the Zap ignores them. Use the Test trigger step and the recent samples Zapier stores (typically the last few within the past hour).

413 responses indicate the payload exceeded the documented size limit; reduce nested data or split events. 429 responses indicate rate limiting; slow the sender or add queuing. Ownership transfer on Team/Enterprise plans changes the URL—update the webhook destination. For deeper diagnosis, catch a raw request and inspect headers and body side by side.

When you need data that the webhook does not carry, call the TrendsAGI REST endpoints or SDK after the Zap triggers. Examples:

# Insights for a known trend ID
curl -H "X-API-Key: $TRENDSAGI_API_KEY" \
  "https://api.trendsagi.com/api/trends/12345/ai-insights"

# Analytics for the last 7 days
curl -H "X-API-Key: $TRENDSAGI_API_KEY" \
  "https://api.trendsagi.com/api/trends/12345/analytics?period=7d"

TrendsAGI webhooks versus native or polling alternatives

TrendsAGI connects to Zapier, Make, and n8n through webhooks and the REST API; there is no native Zapier app. Native actions offered by other trend platforms (for example Exploding Topics as described on explodingtopics.com) can be simpler when they exist, but they are limited to the fields and triggers that platform exposes. Signed webhooks give you the full event shape (velocity, growth, AI summary, themes, sentiment, marketing angles) as soon as TrendsAGI detects the movement.

Polling the REST API with Schedule by Zapier plus a Webhooks by Zapier or API request step is an alternative when you prefer pull over push, but it is not real-time and consumes tasks on a schedule. Choose signed webhooks for low-latency alerts and the API/SDK when you need historical analytics, search across insights, recommendations, or watchlist management.

Frequently asked questions

How do I create a Catch Hook URL in Zapier to receive trending-topic payloads?

In the Zap editor select Webhooks by Zapier, choose Catch Hook (or Catch Raw Hook), continue, and copy the unique URL shown in the Test tab. Paste that URL into the TrendsAGI signed-webhook destination for trend or alert events. Zapier Help documents this flow under “Trigger Zap workflows from webhooks.”

What JSON structure should a trend platform send so Zapier parses fields cleanly?

Send a flat or lightly nested JSON object (or a short array of objects) with consistent keys such as trend_id, name, category, velocity, growth, volume, summary, key_themes, sentiment, and timestamp. Avoid deeply nested or multi-megabyte documents so Catch Hook can expose each field for mapping.

Do I need a paid Zapier plan for Webhooks by Zapier, and what are the payload-size limits?

Webhooks by Zapier is treated as a premium feature; check your current plan in Zapier. Documented payload limits are 10 MB for triggers and 2 MB for Catch Raw Hook. Rate limits include 20,000 requests every 5 minutes per user (with lower limits on certain legacy routes).

How can I verify webhook signatures or handle arrays of multiple trends?

Use Catch Raw Hook to receive headers and the unparsed body, then verify the signature according to the sender’s contract. For arrays, send a JSON array of trend objects and test how Zapier surfaces the items; keep the array short to stay within size and rate limits.

Can I combine this with Exploding Topics native Zapier actions or TrendsAGI webhooks?

Yes. You can run parallel Zaps—one driven by TrendsAGI signed webhooks and another by any native actions a different platform offers—or use TrendsAGI webhooks as the sole real-time source. TrendsAGI has no native Zapier app; webhooks and the REST API are the supported paths.

What are common failure modes and how do I test the trigger?

Common issues are mismatched URLs after ownership change, invalid payload format, oversized bodies (413), and rate limiting (429). Test by sending a curl POST with a minimal JSON body, then use Zapier’s Test trigger and recent samples. Retry with exponential backoff on non-200 responses and keep payloads compact.

Sources

• Webhooks by Zapier Integrations — zapier.com
• Trigger Zap workflows from webhooks (Zapier Help) — help.zapier.com
• Easily Integrate Exploding Topics With Zapier and n8n — explodingtopics.com

Try it with TrendsAGI

• All TrendsAGI integration guides
• TrendsAGI API documentation
• More guides and trend analysis