Skip to main content
Triggers are the starting point of a Zap: something happens, and Zapier runs your workflow.

​
Current Botdog trigger status

Based on the live Botdog integration listing, Botdog currently focuses on an action-first setup (add contacts into Botdog campaigns). If you do not see Botdog trigger events in your Zap editor, start from another app as the trigger and use a Botdog action next.

​
Using a Botdog webhook as a Zap trigger

Until Botdog ships native Zapier triggers, the supported way to start a Zap from something happening in Botdog is a Webhooks by Zapier trigger fed by a Botdog webhook:
  1. In Zapier, create a Zap with Webhooks by Zapier → Catch Hook as the trigger and copy the custom webhook URL it gives you.
  2. In Botdog, go to Settings → Integrations → Webhooks, create a webhook pointing at that URL, and subscribe to the events you care about — commonly Invitation accepted and Received a reply. See Events and payloads for what each one sends.
  3. Let one real event through, then use Test trigger in Zapier to pull that delivery in as the sample.
  4. Map the fields into your next step (a Google Sheets row, a CRM record, a Slack message).

​
Pull a fresh sample after Botdog adds fields

Zapier builds its list of mappable fields from the sample it has already captured, not from the next delivery. When Botdog adds fields to a payload — as it did on 2026-09-23, adding job title, location and 19 others — an existing Zap keeps showing the old, shorter field list until you re-pull a sample. If a field documented on Events and payloads is missing from your Zap editor, that is almost always why: open the Zap’s trigger step and Test trigger again to capture a current delivery.

​
Build from a real delivery, not only a test event

Send test event in Botdog is for checking that your endpoint is reachable and your signature check works. Build your field mapping against a real delivery where you can — a test event carries stub contact data, and before 2026-09-23 it also sent the event label under a slightly different name than real deliveries did, so a mapping built from a test event could come through blank once real events started arriving. Test events now match production exactly, but if you built a Zap from one before that date, compare it against a real delivery in your webhook’s history.

​
Matching a webhook back to your own records

If your Zap writes into a CRM or a sheet you already keep, match on leadLinkedinUrl or leadName — those are exactly what you imported, character for character, so they always equal your own copy. Better still: anything you passed as a Custom Attribute when adding the contact (see Zapier Actions) comes back on every event under leadCustomAttributes, keyed by your own column name. Put your CRM record id in there at import time and the round trip needs no name matching at all.

​
Source of truth

Zapier maintains the authoritative, real-time list of Botdog triggers and actions. Open Botdog on Zapier to see current triggers and templates.

​
Typical flow when triggers are unavailable

  1. In Zapier, create a new Zap and choose another app (for example, HubSpot, Google Sheets, Airtable, or Slack) as the trigger.
  2. Connect your Botdog account using your API key. See Zapier App Authentication.
  3. Add a Botdog action to push contacts into a campaign.
  4. Test and publish the Zap.
If Botdog does not offer a trigger you need, consider starting the Zap from another app (for example, your CRM or a spreadsheet) and use a Botdog action to push data in. For custom logic, use Webhooks by Zapier or the HTTP API from Quick start.