Your Clay table and Slack alerts went quiet after Trigify. How to fix them.

Why did it break without an error?

Trigify pushed data out. Its help centre describes an HTTP Request node that posts to a URL, such as a Clay table’s webhook, plus native nodes for HubSpot, Attio, Salesforce and Airtable, and a route to Google Sheets through the Sheets API or a Zapier webhook. When Trigify stopped, nothing called those URLs any more. The receiving end is still there and still healthy; it is waiting for a sender that is gone.

That is why a table with no new rows and a Slack channel with no new alerts look the same as a quiet week. Nothing failed on your side, so nothing on your side raised an alarm.

How do you find everything Trigify fed, in ten minutes?

1. 01Clay. Open each table and look for a webhook source. Any table whose last row arrived on or before your end date was probably fed by Trigify.
2. 02Zapier. Filter your Zaps by the Catch Hook trigger and check the last run date on each. A webhook-triggered Zap with no runs since your end date is a candidate.
3. 03Make. Open Webhooks and look at each custom webhook’s last activity. Make deactivates a webhook that is not connected to any scenario for more than five days, so check scenarios you paused too.
4. 04Your CRM. Search workflows and lists for a source or property named after Trigify. HubSpot, Attio and Salesforce each had a native node, so records may carry a Trigify source value.
5. 05Slack. Search your channels for the last message from the Trigify app or the Zap that relayed it.
6. 06Sequences. Any sequence that enrolled people from a Trigify list stopped getting new people. It did not stop sending to the ones already in it.

Write each one down with what it did in one line. That list decides what you replace, and some entries on it will turn out to be things nobody needs.

How do you re-point a Clay table?

Clay takes outside data through a webhook source on a table: Add, search for Webhooks, choose Monitor webhook, then copy the URL into the new tool that will post to it. Two limits matter. A webhook source accepts 50,000 submissions, and the count holds even after you delete rows, so a busy feed needs a new webhook once it fills, unless you are on Enterprise with passthrough tables. Clay’s pricing page lists automating a signal by webhook on its Growth plan.

If you regenerate a webhook URL in Clay, the old one stops working. Update the sender in the same sitting.

How do you re-point Zapier and Make?

In Zapier, a Catch Hook trigger gives a unique URL that another app can post to; you find it on the Test tab of the Zap editor. Keep the Zap, paste its URL into the new source, send one test, and remap the fields, because the new sender will not name them the way Trigify did. A Zap that is off answers webhooks with a 404, so a new source reporting errors usually means the Zap was switched off.

In Make, the same job is the Custom webhook module of the Webhooks app. Reconnect the webhook to its scenario before you point anything at it, since an unconnected webhook is deactivated after five days.

What do you point them at now?

Any of the signal tools in our alternatives guide can post to a webhook; Octolens lists webhooks on every plan, and Buska and Clay on their middle plans. Pick the source by the job, then do the plumbing above once.

InstinctGTM is one source you can point them at. In Settings, Webhooks, paste the address Clay, Zapier or Make gave you and tick the events it should hear: engager.new when somebody engages with your posts for the first time, account.changed when a company you watch changes, mention.new for a public thread about what you sell, and deal.created and deal.stage_changed. Send a test from the same screen so the receiver has a first record to map.

Every request is signed with a secret shown to you once, and the format is our own, published and versioned, so map the fields once rather than expecting Trigify’s names. A receiver that stops answering is retried, then switched off, and you get an email about it instead of silence.

The webhook events and what each one carries

It also covers the step after the table: when changes add up at a company you watch, it drafts the message for you to approve, with the dated evidence attached. For some small teams that removes the table altogether.

How do you make it fail loudly next time?

• Add a daily check that counts new rows per feed and posts to Slack when a feed that usually gets some has had none for three days.
• Give every feed an owner, in writing, so “the alerts stopped” reaches one person.
• Keep a copy of every signal in a table you own before it fans out, so a dead source never takes the history with it.