Zapier

There is no Seegnals app in the Zapier directory. You connect with Zapier’s own building blocks, which takes about the same number of clicks and gives you every event and field.

Trigger: something happened in Seegnals

1. In Zapier create a Zap with Webhooks by Zapier → Catch Hook as the trigger. Copy the URL Zapier gives you.
2. In Seegnals go to Settings → Integrations → Webhooks, paste the URL, save.
3. Press Send test event so Zapier has a sample to map fields from.
4. Add Filter by Zapier: continue only when type (Text) exactly matches the event you want.

type	Label	Use it for
sent	Message sent	logging activity in a CRM or a sheet
replied	New reply	creating a task, alerting a channel
clicked	Link clicked	routing hot interest
bounced	Message bounced	cleaning your CRM
unsubscribed	Unsubscribed	syncing opt-outs everywhere

There is no opened trigger and there will not be one; see Webhooks for why.

Fields available in the Zap: id, type, occurred_at, workspace_id, prospect_id, prospect_email, campaign_id, campaign_name, and the metadata keys for that type (for a reply: replyId, from).

Signature verification is optional hardening in Zapier. If you want it, add a Code by Zapier step implementing the check from Verifying signatures.

Action: add a prospect from Zapier

Use Webhooks by Zapier → POST (or Custom Request):

• URL: https://app.seegnals.com/api/v1/prospects (add ?campaign=<id> to enrol at the same time)
• Payload type: json
• Data: email, and optionally first_name, last_name, company_name, timezone, custom_fields
• Headers: Authorization: Bearer sgn_… (create the token in Settings → Integrations → API keys)

To update an existing prospect use Custom Request with method PATCH and URL https://app.seegnals.com/api/v1/prospects/<id>; remember that PATCH expects the full desired state (Prospects).

Action: exclude an address

POST to https://app.seegnals.com/api/v1/suppressions with { "target": "jane@example.com" }. A domain works too. A 409 means it was already excluded.

Revoked tokens

If you revoke the token a Zap uses, its next run gets HTTP 401 immediately. Seegnals never answers 500 for a bad or revoked token, so the Zap fails cleanly and tells you why.

Advanced: subscriptions instead of one URL

If you would rather have one Zap per event with no filter step, create a subscription per event key with POST /api/v1/hooks, each pointing at its own Catch Hook URL.