Peak Automations · Triggers
A trigger starts the automation: an event in Peak One such as a completed task, a won deal or a submitted form, a schedule, a webhook, a manual start or an event from an app your workspace has connected.
Pick your first trigger in Peak AutomationsIllustrative example · sample data · nothing runs
01 / Example value
How completely is your trigger set up?
No test possible · connect under Integrations first
Change the example value. The next step follows the check.
Sample data · nothing runs
Two example values
Schematic example on a scale from 0 to 10. In the product the check lists every missing connection one by one.
Trigger “form submitted” in Peak Forms: lives in your workspace, no connection needed.
No test possible · connect under Integrations first
Start a test run · active only after a passed test
Trust needs clarity
01 / The existing evidence
Peak Automations does not offer other apps than those listed as triggers today. A webhook is the way for everything else.
02 / Your check
Triggers for “has changed”, “nothing happened for X days” or “value exceeds Y” are planned, not built.
Compare both paths and their reasons.
03 / The clear limit
Someone in your workspace connects external accounts under Settings → Integrations. This page connects nothing.
The next step
Start Peak Automations, describe your routine and see which trigger Peak proposes for it.
Pick your first trigger in Peak AutomationsIllustrative example · sample data · nothing runs
Today Calendly, Typeform, Stripe payments, Shopify orders, Gmail and HubSpot through Pipedream. For everything else there is the webhook trigger.
Not yet. Triggers for changes, inactivity and thresholds are planned.
A person in your workspace under Settings → Integrations. Peak connects nothing on its own.
