Webhooks

Project88 supports webhooks in both directions: receiving external HTTP requests into an automation, and sending HTTP requests out from the Automation editor.

Inbound — Webhook trigger node

Drop a Webhook trigger node (WebhookTriggerNode.jsx) into an automation to expose a public URL that fires the workflow on request.

In the inspector:

• Path — URL fragment to listen on.
• Method — POST, GET, or PUT.

The full URL is shown in the inspector. Once the automation is saved, hit that URL — the workflow runs immediately, and the body is available downstream as {{Webhook.output}}.

There's no auth field on the trigger today. For sensitive webhooks, verify the request inside the graph — an early Condition node can check a shared-secret header, and a Code node can verify an HMAC signature before allowing the rest of the workflow to run.

Use inbound webhooks to:

• Receive Stripe / Shopify / Twilio / GitHub / Telnyx webhooks.
• Bridge external cron jobs to a workflow.
• Wire custom UI events in your own product to a Project88 flow.

Outbound — REST API Request node

The REST API Request node is a full-featured HTTP client built into every workflow editor. The inspector gives you:

Hit Play on the node and the Logs panel shows:

• The built request (full URL, headers, body)
• The response status and headers
• The response body as an expandable JSON tree

This is the right node for calling any REST API from inside a workflow — your CRM, your billing system, your internal tools.

Securing inbound webhooks

For sensitive webhooks (Stripe, GitHub):

• For HMAC-signed webhooks, verify the signature inside a Code node before continuing.
• Add an early Condition node that drops requests with missing / invalid headers.
• Rotate webhook URLs by changing the trigger's path if a URL leaks.

Built-in signed / shared-secret options on the trigger inspector itself are a future addition.

Where to next

• Triggers
• Workflow basics
• Telnyx SMS — uses webhooks for inbound