Zapier

The Zapier integration lets you route Auto-Respond leads into any of Zapier’s 6000+ connected apps. Use it when your CRM isn’t one of the directly supported ones, or when you need to fan a single lead out to multiple tools at once (for example, CRM + Google Sheets + Slack + a custom database).

How this integration is different

Unlike the other CRM integrations, which push leads directly into the destination, Zapier works by polling. Auto-Respond makes new leads available; a Zap running on your Zapier account checks for new leads on a schedule and retrieves them. Your Zap then does whatever you want with each lead — create a row, send an email, fire a webhook, etc.

The practical difference is that leads appear in your downstream apps as often as your Zap polls. This is how Zapier works for most polling-style triggers.

What gets made available to Zapier

Each new lead is surfaced to Zapier with:

• First name / last name
• Phone number
• Email
• Postal code
• Source name
• The inquiry / message
• Timestamp

From there, your Zap decides which fields map to the destination app.

Connecting Zapier

Options

Enable

Turns the integration on or off for this source. Default: off.

Inherit from parent

Only shown on a location with a parent business. When on, the location uses the parent’s Zapier API key and settings. When off, it overrides them.

Create customer only when contact info is captured

Default: off.

• When on — The lead is only made available to Zapier once a phone number or email is captured.
• When off — The lead is made available from first contact, even without contact info.

Create only for new leads

Default: off.

• When on — Leads matching an existing entry (by phone or email) are not re-surfaced.
• When off — Updates to existing leads can be picked up by your Zap.

Include source name

Default: off.

• When on — The source name is included in the data your Zap receives.
• When off — The source name isn’t included.

Validate Connection

Re-tests your Zapier API key.

Disconnect

Removes the API key. Confirmation required.

When to use Zapier instead of a direct CRM integration

• Your CRM isn’t one of the nine directly supported ones.
• You want to route the same lead into multiple apps at once.
• You need custom logic between Auto-Respond and the destination (filters, formatters, branches).
• You’re already a Zapier shop and want all your integrations in one place.

If you’re using one of the directly supported CRMs (HubSpot, PipeDrive, Workiz, GoHighLevel, HousecallPro, SmartMoving, Salesforce, Monday.com), use the direct integration — it’s faster and more reliable than polling.

Disconnecting

Open the Zapier card → click Disconnect → confirm. The API key is cleared. Your Zaps on zapier.com will start failing until you reconnect with a valid key (or turn off the Zap).

Troubleshooting

• “Validation failed” / invalid key — The Zapier API key is wrong. Re-copy it and paste again.
• My Zap says there are no new leads — Confirm Enable is on. Check that the Zap is turned on in Zapier and that the polling interval isn’t set so long that you just haven’t hit it yet.
• Leads show up on Zapier but I didn’t want certain ones — Use a Filter step in Zapier. For example, only continue if the phone number is present.
• Duplicates in my downstream app — Add a Zapier deduplication step on your Zap, or turn on Create only for new leads in Auto-Respond.

Questions about the Zapier integration? Email support@auto-respond.com.