A webhook is a message Perform sends to another system’s address when something happens. The Webhook step lets any automation hand an event to Make, Zapier, n8n or your own system. Use it when the follow-up lives outside Perform, for example adding a row to a spreadsheet, creating an invoice or posting to a team chat.

​
Add a webhook to a flow

1

Get an address from the other system

In Make, add a “Custom webhook” module and copy the address it gives you. Other tools have a similar “catch a webhook” step.
2

Add the step in Perform

Open the automation, click the plus button and choose Webhook.
3

Fill in the step

  • Friendly name: a label so you know what this webhook is for.
  • URL: paste the address.
4

Check it for real

Let the automation fire once for a real trainee, then look at the history in the other system to confirm the event arrived.
The Send test button in the step does not call your address. It only marks the step as tested in the builder. The same goes for Run test on the canvas, which uses sample trainees and sends nothing. The only real test is a real run.

​
Address rules

  • The address must start with https://.
  • It must be a public address. Local and private network addresses are refused.
  • An address that breaks these rules cannot be saved.
  • A step with an empty address can be saved. It is skipped when the flow runs.

​
What is sent

Each time the step runs, Perform sends one message with these details: In the other system, map these fields into the next modules of your scenario.
The message does not include the form answers, the task or the reason behind the trigger. To receive the full answers of a filled form, connect the tool with a studio API key and use its “form filled” trigger. See Connecting Make and other tools.

​
If the other system does not answer

  • Perform waits up to 10 seconds for an answer.
  • If the other system is down or answers with a server error, Perform tries again, up to 5 times in total. The gap between tries grows each time, starting at about 10 seconds.
  • If the other system rejects the message as wrong, Perform does not try again. A “too many requests” answer is the exception and is retried.
  • The flow does not wait for the webhook. The next step runs straight away, whether or not the message has been delivered yet.
Perform has no screen that lists webhook deliveries. Check the history in the receiving system.

​
Privacy

The webhook sends a trainee’s name, phone and email to the address you enter. Only use addresses that belong to tools your studio trusts, and remove the step when you stop using that tool.

Connecting Make and other tools

Let a tool read and change studio data with an API key.

Actions

The other steps you can add.