FIG. 01 INTEGRATIONS

If it speaks webhooks, it speaks Notebooker.

Trigger workflows from any service that sends them, and push events out to anything with a URL. INCOMING - a service calls Notebooker. OUTGOING - Notebooker calls a service.

INCOMING · OUTGOING

Slack

Post notebook updates to channels; trigger workflows from Slack events.

WEBHOOK DOCS →

INCOMING · OUTGOING

Discord

Send messages to channels through webhook URLs; receive interaction events.

WEBHOOK DOCS →

INCOMING

Microsoft Teams

Post cards and notifications to Teams channels via incoming webhooks.

WEBHOOK DOCS →

INCOMING · OUTGOING

Zapier

Trigger Notebooker workflows or fan events out to thousands of apps.

WEBHOOK DOCS →

INCOMING · OUTGOING

Make

Build no-code automations that send to or receive from Notebooker.

WEBHOOK DOCS →

INCOMING · OUTGOING

n8n

Self-hostable automation with first-class webhook support - a natural fit.

WEBHOOK DOCS →

INCOMING · OUTGOING

IFTTT

Fire IFTTT applets from Notebooker, or trigger workflows from applets.

WEBHOOK DOCS →

OUTGOING

GitHub

Subscribe to repository events - push, PR, issues - and trigger workflows.

WEBHOOK DOCS →

OUTGOING

Linear

Get notified about issue, project, and comment changes in your workflows.

WEBHOOK DOCS →

OUTGOING

Notion

Subscribe to database and page changes with Notion's webhook events.

WEBHOOK DOCS →

OUTGOING

Stripe

Receive payment, customer, and subscription events for billing-aware flows.

WEBHOOK DOCS →

OUTGOING

Trello

Listen for board, list, and card events with Trello's webhook API.

WEBHOOK DOCS →

INCOMING · OUTGOING

Telegram

Bot webhooks send notifications to chats and receive updates as triggers.

WEBHOOK DOCS →

INCOMING · OUTGOING

Anything else

Any service that can POST JSON can trigger a Notebooker workflow, and any workflow can POST to any URL. That's the whole trick.

WEBHOOK DOCS →

FIG. 02 HOW IT WORKS UNDERNEATH

Webhooks are powered by Workflows

A visual builder for what happens when an event arrives, and what goes out when something happens.

INCOMING

Every workflow gets a unique URL. Point any service at it and the request body becomes the workflow's input.

  1. Create a workflow, choose the Webhook trigger
  2. Paste the generated URL into the external service
  3. Send a test payload - it runs immediately
OUTGOING

Add an HTTP Request step to any workflow to POST anywhere - headers, templated JSON body, captured response.

  1. Open a workflow, add an HTTP Request step
  2. Paste the destination URL
  3. Template the body with variables from earlier steps
Build a workflow Missing your tool? Tell us - if it webhooks, we'll list it.