Peak Automations / SaaS
Your product sends a signal.A person on the team gets the matching task.
SaaS teams have signals from the product and from billing. Peak Automations receives events through a webhook trigger with its own key and payments from Stripe, creates or updates contacts and gives the team a task or a Slack message.
Put the goal into words. Add perspectives and timing right below.
Two sample flows · webhook trigger, no dedicated automations API.
One webhook / one payment
Signal, contact, task.
- Trigger
- Webhook from your product or Stripe payment.
- Steps
- Create or update contact, task, Slack message.
- Control
- Repeated webhooks are processed only once.
Your first automation
Which signal should arrive?
Set the event, the owner and the first step. The preview shows the rule and stores nothing.
Local working example · nothing is saved or sent. Please don't enter personal data.
Three answers. A signal with a consequence.
Draft · not yet put together
- Trigger
- Still open
- Người phụ trách
- Still open
- First step
- Still open
Two signals
Which signal should reach the team?
Pick the signal. The example shows what Peak makes of it.
Event from your product
Your product calls the automation's webhook.
- The action
- Peak finds or creates the contact by email and creates the task “offer a welcome call” for customer success.
- The intent
- New teams have a contact person right away.
Example: webhook → welcome
- When
- Webhook “team.created” (example)
- Then
- Create or update contact
- And
- Task “welcome call”
The example shows the structure. In Peak Automations you describe what should follow a product event.
To the next stepIs this for you?
What works today. What doesn't yet.
A SaaS team that
turns product signals into team work.
This is where the example helps.
- Your product can call a webhook.
- Billing runs through Stripe.
- Signals should land with people, not in logs.
Nothing runs
What Peak Automations doesn't do today.
- There are no dedicated API endpoints for automations; only the webhook trigger.
- Triggers on usage thresholds are planned, not available today.
- Revenue or ROI attribution per automation is planned, not available today.
From the example to a real automation
Connect your first product signal.
Describe the event, let Peak create the webhook trigger and test it with a sample payload before switching on.
Start with Peak AutomationsPeak Automations / Your next step
Signals that reach someone.
Start with the product event nobody reacts to today.
See SaaS examples
For SaaS teams between product and customer.
Repeated webhooks are processed only once.
Frequently asked questions
Are these real customer cases?
No. They are examples built from triggers and actions that exist today. We only show customer cases with evidence.
Does an automation start running right away?
No. You test it with an example first and then activate it yourself. Nothing runs before that.
How is the webhook protected?
Every automation with a webhook has its own key. Without it Peak does not accept the call.