Skip to content
Peak Atlas

Peak Automations · Developers and webhooks

Your system calls.
Peak Automations listens.

Built today is the webhook trigger: an automation gets its own address with a key, and your system starts it with a POST. The fields of the call are available to conditions and steps. A dedicated API for creating and controlling automations is planned.

Set up a webhook trigger

Example mapping · no call is sent

Your systemThe call
Peak AutomationsThe trigger field
Peak Automations · Example mapping
One mapping in detail
01 / Your systememail
02 / Fictional test valuealex@example.com
03 / Peak AutomationsTrigger · email

A readable field path as an example. No run.

View all 5 mappings
Example fields of a call with fictional values. You decide the real fields in your system.
Your systemField in the trigger
emailTrigger · email
order_refTrigger · reference
statusTrigger · status
noteTrigger · note
sent_atTrigger · time
Example mapping
No run
Today there is only the webhook trigger. An automations API is planned.
One concrete target

Map fields. Keep the source.

Peak AutomationsArrival in the targetNot tested yet

The mapping shows which value from the trigger goes into which step. Only a test run in your workspace shows what actually arrives.

02 / How the webhook trigger works

One address, one key, one queue.

The call does not start a step directly. It puts a run into the queue, with the same checks as any other trigger.

  1. 01 / Today

    Address and key

    Every automation with a webhook trigger has its own address. Without a valid key the call is rejected.

    What exists?Webhook triggerOwn address with keyQueue with retries
  2. 02 / Planned

    Queue the run

    The call lands in the queue. Retries and duplicate protection stop the same call from taking effect twice.

    What is missing?Automations APIQuery runsOutgoing webhooks
  3. 03 / Your path

    Same rules

    Runs started by webhook also need an active, tested version, and risky steps wait for approval.

    What do you do today?Create the addressTest a sample callActivate the version

Trust needs clarity

What does not exist for developers yet.

01 / The existing evidence

No automations API

Endpoints to create or change automations from outside or to query runs are planned. Today there is only the webhook trigger.

Your system / Peak AutomationsEXAMPLE
Your systemField mappingPeak Automations
Mapping
Example
Arrival in the target
Not tested

02 / Your check

No outgoing webhooks as a step

An action that calls an arbitrary webhook is not part of today's building blocks. Outside actions run through the listed integrations.

Connection
Not connected here
Rights
Roles in the workspace

03 / The clear limit

No call on this page

The mapping above is an example. No address is created and no call is sent here.

  • Webhook
  • Key
  • Queue
  • API planned

The next step

Your system as the trigger, Peak for the rest.

Start Peak Automations, pick the webhook trigger and test the automation with a sample call.

Set up a webhook trigger
Your field mappingNOT CONNECTED
Your system→Peak Automations
email → Trigger · email

Check in a test run of your workspace what actually arrived.

Frequently asked questions

How is a webhook protected?

With a key of which Peak stores only a hash.

Is there an API for automations?

Not yet. It is planned. Today there is the webhook trigger.

Does a webhook run right after creation?

No. The same rule applies: test first, then activate.

More in Peak Automations