Zapier / Make.com / n8n Integration Guide

Overview

Orbyt's webhook system sends real-time notifications when events happen in your pipeline: new jobs added, status changes, offers received, interviews scheduled, and more. Connect these webhooks to Zapier, Make.com, or n8n to build powerful automations.

Prerequisites

• Orbyt Ultra plan
• An Orbyt API key with read-write permissions
• A Zapier, Make.com, or n8n account

Webhook Events

Orbyt can send webhooks for these events:

Event	Fires When
job.created	A new job is added to the pipeline
job.updated	Job details are modified
job.deleted	A job is removed
job.status_changed	Job moves to a new status
contact.created	A new contact is added
contact.updated	Contact details are modified
contact.deleted	A contact is removed
activity.created	An activity is logged
interview.scheduled	A job moves to interviewing status
offer.received	A job moves to offer status
webhook.test	Test event sent manually

Setting Up with Zapier

Step 1: Create a Zap with Webhook Trigger

1. Log in to Zapier and click Create Zap
2. For the trigger, search for Webhooks by Zapier
3. Select Catch Hook as the trigger event
4. Zapier gives you a webhook URL like: https://hooks.zapier.com/hooks/catch/123456/abcdef/
5. Copy this URL

Step 2: Register the Webhook in Orbyt

Use the Orbyt API to register Zapier's webhook URL:

curl -X POST https://www.orbytjobs.ai/api/mcp/webhooks \
  -H "Authorization: Bearer ext_your_token" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://hooks.zapier.com/hooks/catch/123456/abcdef/",
    "events": ["job.status_changed", "offer.received", "interview.scheduled"],
    "secret": "my_signing_secret"
  }'

Step 3: Send a Test Event

curl -X POST https://www.orbytjobs.ai/api/mcp/webhooks/test \
  -H "Authorization: Bearer ext_your_token" \
  -H "Content-Type: application/json" \
  -d '{ "webhookId": "wh_abc123" }'

Go back to Zapier and click Test trigger to confirm the test event was received.

Step 4: Add Actions

Now add actions to your Zap. Popular combinations:

When	Then
Job status changes to "interviewing"	Send Slack message to #job-search channel
Offer received	Send email to partner/spouse with details
New job added	Create a card in Notion database
Activity logged	Add row to Google Sheet for tracking
Interview scheduled	Create Google Calendar event with prep notes

Setting Up with Make.com

Step 1: Create a Scenario

1. Log in to Make.com and create a new scenario
2. Add a Webhooks module as the trigger
3. Select Custom webhook
4. Make gives you a URL like: https://hook.make.com/abc123xyz

Step 2: Register the Webhook

Same as Zapier, use the API to register the Make webhook URL:

curl -X POST https://www.orbytjobs.ai/api/mcp/webhooks \
  -H "Authorization: Bearer ext_your_token" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://hook.make.com/abc123xyz",
    "events": ["job.created", "job.status_changed"],
    "secret": "my_make_secret"
  }'

Step 3: Build Your Flow

Make.com's visual builder lets you:

• Filter events by type (only act on offer.received)
• Route to different actions based on job status
• Transform data before sending to other services
• Iterate over arrays (e.g., multiple contacts on a job)

Setting Up with n8n

Step 1: Add a Webhook Node

1. Open your n8n instance
2. Add a Webhook node as the trigger
3. Set the HTTP method to POST
4. Copy the production webhook URL

Step 2: Register and Connect

Register the n8n webhook URL using the same API call pattern above. Then add downstream nodes for your automation logic.

Webhook Payload Format

All webhooks are sent as POST requests with this structure:

{
  "event": "job.status_changed",
  "timestamp": "2026-03-29T14:30:00.000Z",
  "data": {
    "id": "job_abc123",
    "company": "Stripe",
    "title": "Senior Frontend Engineer",
    "status": "interviewing",
    "previousStatus": "applied"
  }
}

Webhook Security

Every webhook includes an X-Orbyt-Signature header containing an HMAC-SHA256 signature of the request body, signed with your webhook secret. Verify this in your automation to ensure the webhook came from Orbyt:

HMAC-SHA256(request_body, your_secret)

Managing Webhooks

# List all registered webhooks
curl https://www.orbytjobs.ai/api/mcp/webhooks \
  -H "Authorization: Bearer ext_your_token"

# Delete a webhook
curl -X DELETE https://www.orbytjobs.ai/api/mcp/webhooks \
  -H "Authorization: Bearer ext_your_token" \
  -H "Content-Type: application/json" \
  -d '{ "webhookId": "wh_abc123" }'

Automation Ideas

Automation	Services
Daily pipeline digest in Slack	Zapier + Slack (scheduled, uses /pipeline endpoint)
Interview prep packet in Notion	Make.com + Notion (triggered by interview.scheduled)
Offer celebration alert	Zapier + Slack/Email (triggered by offer.received)
Job application log in Google Sheets	Zapier + Google Sheets (triggered by job.status_changed to "applied")
Stale application reminders	n8n + Email (scheduled, uses /suggestions endpoint)
Contact sync to HubSpot	Make.com + HubSpot (triggered by contact.created)

Tips

• Register webhooks for specific events rather than all events to reduce noise
• Always set a secret when creating webhooks and verify signatures in your automation
• Use Orbyt's test endpoint to verify your automation works before relying on real data
• Maximum 10 webhooks per user
• Webhooks time out after 10 seconds; if your endpoint is slow, use a queue (Zapier and Make handle this automatically)