Sending automation data to Google Sheets or Zapier

TRIGMAZE doesn’t have a built-in Google Sheets connection — instead, the Webhook node in the flow builder sends a JSON request to any URL you give it, and that’s how you reach Sheets, Airtable, your CRM, or anywhere else: point it at a Zapier or Make webhook trigger, or at a Google Apps Script web app deployed against your own spreadsheet, and let that tool do the writing.

What gets sent

Add a Webhook node anywhere in a flow, paste a public HTTPS URL, and TRIGMAZE POSTs this JSON body when that node runs:

• The contact’s id, Instagram user id, username, tags, and custom fields.
• Any flow variables captured earlier in that run (e.g. a “Capture reply” node’s answer).
• A timestamp and an event name identifying this as a TRIGMAZE webhook node call.

Security limits, on purpose

The URL must be a public, reachable HTTPS (or HTTP) address — TRIGMAZE actively rejects a webhook pointed at localhost, a private/internal network address, or anything that isn’t a normal public endpoint. This isn’t configurable; it’s a safety boundary against a webhook being pointed somewhere it shouldn’t reach.

If the webhook fails

TRIGMAZE makes one attempt per node run, waits up to 8 seconds, and does not retry. If the receiving end is down, times out, or returns an error, the rest of your flow still continues — a broken Zapier zap or a paused Apps Script can’t take your whole automation down with it. There’s no separate alert for a failed webhook call specifically; check that automation’s run log (open the automation → Runs) if you suspect data isn’t reaching the other end, and confirm the receiving tool is actually turned on and reachable.