Zapier integration
Zapier is on the map, not in the product yet.
Our Zapier integration wires pipeline events into thousands of apps without anyone writing code.
How it works
SearchHandled is a public integration on the Zapier platform. It exposes triggers for the moments that matter in the pipeline, an opportunity found, an article published, indexing verified, and an action that lets other apps request an article from your queue. Connecting is Zapier's standard OAuth flow, and from there Zaps compose our events with any of the thousands of apps in Zapier's directory.
In the loop, Zapier is the extension cord. Published articles can append to an Airtable log, indexing verification can update a project tracker, a new opportunity can open a ticket for review, and a form submission elsewhere can request an article from us. Anything the loop emits or accepts becomes something your other tools can react to, with the logic living in Zapier where your team can see and edit it.
Best forTeams whose workflow spans tools we do not integrate directly and who want to wire those connections themselves.
Setup, step by step
- Search for SearchHandled in Zapier's app directory and select it in a new Zap.
- Connect your account through the OAuth prompt Zapier shows.
- Pick a trigger, such as article published or indexing verified, and pull in sample data to map fields.
- Add the action app on the other side of the Zap and map our fields into it.
- Turn the Zap on and watch the first real event flow through Zapier's task history.
Best practices
Start from the sample data
Zapier's field mapping is easiest when built against a real sample. Pull in sample data during setup so every field you map is one you have seen filled, not guessed at.
Keep one job per Zap
A Zap that logs published articles and a separate Zap that alerts on ranking wins are easier to debug than one Zap with branching paths. Small Zaps make the task history readable.
Use the request-article action deliberately
The action that requests an article puts content into your queue, so wire it to intentional signals like an approved form or a CRM stage change, not to anything that fires casually.
Watch task history after changes
When you edit a Zap or we ship integration updates, glance at Zapier's task history for the next few runs. It is the fastest place to see a mapping that no longer lines up.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
The public Beta tag on new integrations
Zapier labels newly published integrations with a public Beta tag for their first 90 days, which can read as unfinished to teams evaluating the connection.
How we handle itThe tag is Zapier's standard policy for every new integration, not a verdict on stability. The triggers and actions behind it are the same production pipeline events the rest of the product runs on.
docs.zapier.com
Field mappings drift when Zaps change
An edited Zap or a changed downstream app can leave field mappings pointing at nothing, and events then arrive incomplete on the other side.
How we handle itOur trigger payloads keep stable field names, and Zapier's task history shows each run's data, so a broken mapping is visible per run and fixable in the Zap editor in minutes.
docs.zapier.com
Questions teams ask
- What triggers and actions are available?
Triggers fire when an opportunity is found, when an article publishes, and when indexing is verified. The action lets another app request an article, which drops a brief into your SearchHandled queue.
- Does using the integration cost extra?
Nothing from us. You need a Zapier account, and Zapier's own plan limits govern how many tasks your Zaps can run, but the SearchHandled integration itself is free to use.
- Why does the integration show a Beta tag?
Zapier applies a public Beta tag to every newly published integration for its first 90 days as standard policy. It reflects the integration's age in the directory, not its reliability.
Not connectable yet
Start with the plan, not the connector.
Build a Growth Map from your site to see the work itself. Approved pages can leave through the export or the webhook today, and telling us Zapier matters moves it up the rollout.