Zapier & Webhooks Both

Connect TapTidy to Zapier, Make, or custom automation platforms using real-time REST webhooks and HMAC-SHA256 signature verification.

Supported Outbound Events

TapTidy dispatches real-time events to active subscription endpoints:

• task.created: Fires whenever a new task is added.
• task.updated: Fires when title, description, due date, project, or priority changes.
• task.completed: Fires when a task is checked off.
• task.deleted: Fires when a task is archived or removed.

Outbound Webhook Delivery & Verification

Each outbound webhook delivery includes authentication and tracking headers:

• Content-Type: application/json
• X-TapTidy-Event: The event name (e.g. task.completed).
• X-TapTidy-Signature: The signature formatted as sha256=<hex_digest>, computed using HMAC-SHA256 over the raw JSON payload with your webhook secret.
• X-TapTidy-Delivery: A unique UUID for the delivery attempt.

Failed deliveries are retried automatically with exponential backoff (1m, 5m, 15m) up to 3 attempts before being moved to the dead-letter log.

Managing Subscriptions

Subscriptions can be managed programmatically via the TapTidy REST API:

• GET /api/v1/integrations/zapier/secret: Retrieve or generate your account HMAC secret.
• POST /api/v1/integrations/zapier/secret/rotate: Rotate your secret and update active subscriptions.
• POST /api/v1/integrations/zapier/subscriptions: Register a new webhook target (targetUrl and optional eventTypes array).
• GET /api/v1/integrations/zapier/subscriptions: List all active subscriptions.
• DELETE /api/v1/integrations/zapier/subscriptions/:id: Remove a subscription.
• GET /api/v1/integrations/zapier/deliveries: Review recent delivery statuses and attempts.

Inbound Webhooks (Triggering TapTidy)

To create or update tasks from external platforms like Zapier, send a POST request to /api/v1/integrations/zapier/inbound with an X-Zapier-Signature: sha256=<hex> header. Supported actions include create_task and update_task.

Authentication & Scopes

Webhook management endpoints require Bearer authentication using a Personal Access Token or App Password with the tasks:write and tasks:read scopes.