Connect Semwiser to Zapier
Send Semwiser events to any app with a Zapier webhook, and create leads over the API.
Semwiser is not listed in Zapier’s app directory yet. You connect it today with Zapier’s own webhook steps: no code, and nothing to install.
Send Semwiser events to Zapier
- 1In Zapier, start a Zap with the Webhooks by Zapier trigger, choose Catch Hook, and copy its URL.
- 2In Semwiser, open Account → Developers and add a webhook as an Endpoint with that URL.
- 3Your events are sent to that URL: scan.completed, scan.failed, rank.changed, reputation.feedback.created and lead.created, plus site_audit.issue when you click Send on an issue in SEO. A webhook takes your whole team’s events: a scan a teammate runs, or a review that comes in on their side, reaches it as well as your own, and so does a teammate’s lead when you can see every lead in the CRM. Someone who sees only chosen clients gets their own events, and an SEO issue goes only to the destinations of the person who sends it. Add a Filter step in Zapier to keep only the events you want.
- 4Make an event happen (for example, run a scan), test the trigger in Zapier, then finish your Zap.
Create leads from other apps
To add a lead to your Semwiser CRM from another app, call the REST API from a Webhooks by Zapier POST step: send it to your Semwiser app address followed by /api/v1/crm/leads, set Payload Type to JSON, add the header Authorization: Bearer zk_…, and include at least one of full_name, email or phone. Pass a source_ref and the same record never creates two deals.
Example Zaps
- scan.completed → post the result to Slack, or add a row to Google Sheets for reporting.
- reputation.feedback.created → tell your team when a customer leaves private feedback.
- A new enquiry in your web form → create a lead in Semwiser with the POST step above.
Good to know
- Deliveries are instant: Semwiser posts to your URL the moment the event happens.
- Slack and Discord can also be connected directly under Account → Developers, without Zapier.
- The API allows 120 requests per minute per person, shared by every API key you create and every SI assistant you connect. Each teammate has their own 120. The count starts again at the top of every clock minute, and a call over the limit gets HTTP 429 with a Retry-After header: the number of seconds until that minute ends. Wait that long, then send it again.
- API keys and webhooks can require the GBP Management plan.