Zapier connects Examply to thousands of other apps without writing any code. Webhooks deliver the same events in raw form, sent directly to a URL you control, for when you need more flexibility than a Zap provides.
Reach for Zapier first if you want something running in minutes and the app you're connecting already has a Zapier integration. Reach for webhooks if you're building something custom, need lower latency, or want to send events to an internal system that Zapier doesn't support.
Note: Zapier requires a Starter plan or higher. Webhooks require a Pro plan or higher.
Using Zapier
In Zapier, search for the Examply app and choose it as a trigger or action.
Sign in to Examply and authorize Zapier to access your workspace.
Choose a trigger, such as New task or Task completed, or an action, such as Create task.
Map fields from the connected app to Examply fields, then turn on the Zap.
A common Zap creates a task in Examply whenever a row is added to a Google Sheet, or posts to a Slack channel whenever a task is completed in a specific project.
Setting up a webhook
Go to Workspace settings → Integrations → Webhooks.
Click Add endpoint and enter the URL that should receive events.
Select which events to send.
Save the endpoint. Examply signs every request with a secret shown on this screen, so you can verify it came from Examply.
Examply sends a POST request with a JSON body for every event:
{
"event": "task.completed",
"task_id": "EX-1042",
"project": "Website relaunch",
"completed_by": "priya@examply.com",
"completed_at": "2026-07-14T15:32:00Z"
}
Available events
Event | Fires when |
| A new task is added to a synced project |
| A task is marked complete |
| A task's assignee changes |
| A new project is created in the workspace |
| A project is archived |
Verifying a webhook payload
Every webhook request includes an X-Examply-Signature header, computed from the payload and your endpoint's secret. Recompute the signature on your end and compare it before trusting the request. This stops anyone else from sending fake events to your endpoint even if they guess the URL.
Troubleshooting
If a webhook endpoint stops receiving events, check its status on the Webhooks settings page. Examply disables an endpoint automatically after repeated delivery failures. Re-enable it once your endpoint is back up, and Examply resends events from the point it stopped where possible. For Zapier issues, check the Zap's task history in Zapier first, since most failures come from a missing or renamed field in the connected app.