Skip to Content
SyncGTM PlatformWorkspace controlsWebhooks

Webhooks

A webhook gives your table a URL that external tools can POST to. Every payload that arrives creates rows — see Webhooks and HTTP for how to set one up.

View Table Webhooks is the other half of that: the list of endpoints already attached to this table.

What it does

  • Lists every webhook endpoint pointing at this table
  • Shows the URL to copy back into Zapier, Make, Stripe, a form tool, or your own backend
  • Gives you one place to check what is creating rows before you go hunting through external tools

How to view them

  1. Click the ⚙️ icon in the top-right of the table
  2. Click View Table Webhooks
  3. Copy the URL you need, or check which integration owns it

To create a new one, go to Table → Import → Webhook instead.

When to check this screen

  • Rows are appearing and you do not know why. An old automation is still POSTing.
  • You are handing a table over. Confirm what is wired in before someone else owns it.
  • You turned on Auto-run. Every incoming row now triggers every action column — know your inbound volume before you flip that switch.
  • A form or payment tool changed. Re-copy the URL rather than guessing which endpoint it was using.

A webhook URL is a write endpoint for your table. Treat it like a credential — anyone holding it can create rows, and with Auto-run on, those rows spend credits.

Further automation

  • Point your website form at the webhook, enrich on arrival, and export to your sequencer — an inbound lead worked in minutes
  • Send closed-won deals from your CRM into a table to build lookalike lists
  • Use an HTTP Request action to push the enriched row back out to the tool that sent it

Common use cases

  • A website form or demo request creating rows in real time
  • Events from Stripe, Zapier, Make, or a form tool
  • A CRM pushing new or updated records into a table
  • Your own backend posting rows from an internal app
  • Working out what is creating rows you did not expect

Best practices

  • Use one webhook per source so you can tell which tool owns which endpoint
  • Check this list before turning Auto-run on — every inbound row will then trigger every column
  • Treat the URL like a credential: anyone holding it can create rows and spend credits
  • Re-copy the URL from here when a tool changes, instead of guessing which endpoint it used
  • Remove endpoints nobody owns any more before handing the table to someone else

Where to next

Auto Delete Old RowsShare as Template