Skip to content
Journeybee Help Center home
InboxAsk a human

Zapier

You can wire Journeybee into Zapier, or Make, n8n, Workato, or anything else that speaks HTTP, using the Journeybee public API and an API key. Journeybee can push events out the moment they happen (a new lead, a won deal, a completed payout), and Zapier can create and update Journeybee records in return.

Where to find it: API keys live in Settings, then API Keys. There is nothing to connect on the Integrations page.

Who can use this: Admins create API keys. Your company needs the API & MCP module enabled, so contact Journeybee support if the API Keys page is not available to you.

Before you start

Journeybee does not yet have a listed app in the Zapier directory, so you build Zaps with Zapier's own Webhooks by Zapier steps. Everything below works today with no waiting list. It is just a little more hands-on than picking an app from a menu.

The two pieces you need:

  • An API key from Settings, then API Keys. Choose Read for anything that only fetches data, and Write if your Zap will create or update records. Copy the key when it is shown, because you cannot see it again. See API Keys.

  • The API base URL: https://api.journeybee.io/v1, with the header Authorization: Bearer YOUR_API_KEY.

Triggers: Journeybee to Zapier

Journeybee can POST to a URL the moment something happens, which is exactly what a Zapier catch hook wants.

  1. In Zapier, create a Zap starting with Webhooks by Zapier, then Catch Hook. Copy the custom webhook URL it gives you.

  2. Subscribe that URL to the event you care about:

    curl -X POST https://api.journeybee.io/v1/webhooks/subscriptions \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "integration_id": 42, "event": "leads.create", "url": "https://hooks.zapier.com/..." }'

    Ask Journeybee support which integration_id to use for self-serve subscriptions.

  3. Trigger the event once in Journeybee so Zapier can capture a sample payload, then build the rest of your Zap as normal.

Events you can subscribe to

  • Leads: created, updated, deleted, and notes created, updated or deleted.

  • Deals: created, updated, deleted.

  • Partners: created, updated, and partner contacts created or updated.

  • Payments: payout initiated, completed or failed.

  • MDF: claim payout completed or failed.

Each delivery arrives as a JSON POST carrying an Authorization: Bearer token signed for your integration. Verify it before acting on the payload if your endpoint is public.

Actions: Zapier to Journeybee

To write into Journeybee, use Webhooks by Zapier, then Custom Request, against the API:

  • Method: POST to create, PATCH to update, DELETE to remove.

  • URL: the endpoint you want, for example https://api.journeybee.io/v1/leads or https://api.journeybee.io/v1/partners.

  • Headers: Authorization: Bearer YOUR_API_KEY and Content-Type: application/json.

  • Data: the JSON body for that endpoint.

Typical Zaps: create a Journeybee lead when a form is submitted elsewhere, update a deal when your finance system marks an invoice paid, or add a partner when a new account is created in another tool.

Records are addressed by their uuid, which every response includes. Store it in your Zap if you plan to update the record later.

Polling instead of webhooks

If you would rather not manage a subscription, a scheduled Zap can call a list endpoint (for example GET /v1/leads) on an interval and work through the results. List endpoints are paginated, and responses carry a pagination block with the page, page size and total. Use it rather than assuming you got everything in one call.

Limits

  • 500 requests per minute per API key. Going over returns 429 Too Many Requests with a Retry-After header. Respect it and retry after the delay.

  • A Read-only key gets 403 Forbidden on any write. Create a separate key with Write if a Zap needs to change data.

  • Subscription URLs must be HTTPS.

Troubleshooting

  • 401 Unauthorized. The key is missing, mistyped, or revoked. Check the header reads Authorization: Bearer YOUR_API_KEY, the whole value, including the word Bearer.

  • 403 Forbidden. Either the key is Read-only and the Zap is trying to write, or the API & MCP module is not enabled for your company.

  • 429 Too Many Requests. You are over 500 requests a minute. Add a delay step, or batch your work.

  • The Zap never fires. Confirm the subscription was created for the right event name and that the catch-hook URL was copied in full. Trigger the event manually in Journeybee to test.

  • Fields are missing from the payload. Webhook payloads carry the core record. For everything else, follow up with a GET on that record's endpoint using its uuid.

Good to know

  • Treat API keys like passwords. Do not paste them into shared docs, and revoke any key that leaks. See API Keys.

  • For automation that stays inside Journeybee (stage changes, reminders, assignments, emails), use Workflows. It needs no external tool and no API key.

  • The same API key also works with the Journeybee MCP server, if you would rather point an AI assistant at your data than build a Zap.

  • Full endpoint reference, schemas and SDK details live in the Journeybee API documentation at docs.journeybee.io.