Getting started

This walks through the smallest useful workflow: a webhook that posts a message to Slack. It takes a few minutes and touches every core concept - triggers, nodes, credentials, and execution status.

1. Sign up

Pipory uses Clerk for authentication - email/password and social login. Create an account or log in, and you land on your workflow list.

2. Create a workflow

Click New workflow from the workflow list. A new workflow opens in the canvas editor with a single placeholder node - pick a trigger to replace it and the workflow becomes editable.

3. Add a Webhook trigger

Open the node palette and add a Webhook node as your trigger. Pipory gives the workflow a unique URL in the shape /api/webhooks/wf/[workflowId], guarded by a per-workflow secret. Open the node's dialog to copy the URL and the secret (or regenerate the secret if you need a fresh one).

The secret must be sent as either:

• an x-webhook-secret header, or
• a ?secret= query parameter

A request with a missing or wrong secret gets a 401. A request that matches is accepted and its JSON body becomes available to every downstream node as {{webhook.x}} (see Workflows for how that resolves).

4. Add a Slack node

Connect a Slack node after the trigger. Slack posts through an incoming webhook URL, so there is no OAuth flow - paste the channel's webhook URL when configuring the node, then template the message text, for example:

New signup: {{webhook.email}}

5. Run it

Click Execute workflow in the editor toolbar to fire a manual test run right away, or send a real request to your webhook URL:

curl -X POST "https://pipory.com/api/webhooks/wf/<workflowId>" \
  -H "x-webhook-secret: <secret>" \
  -H "Content-Type: application/json" \
  -d '{"email": "ada@example.com"}'

As the run executes, every node on the canvas updates its live status in place - running, done, failed, or skipped - streamed live to the canvas. No page refresh needed.

6. Check the execution log

Open Executions from the sidebar to see the run: status, duration, and a per-node timeline with each node's resolved input and output. This is the same log the workflow chat assistant reads when explaining a workflow, and it is where you go first when something fails - see Executions.

Where to go next

• Workflows - the canvas, nodes and edges, and how Handlebars context resolves.
• Triggers - every way to start a run.
• Flow control - branching, loops, delays, and error handling.
• Templates - 37 ready-made workflows if you'd rather clone than build from scratch.