Peak Automations / After the signature
The contract is signed.And now everyone waits.
Time often gets lost between the signature and the first project day because nobody kicks off the start. Peak Automations knows the trigger “agreement signed” from Peak Sign. It becomes a started flow, tasks for project lead and accounting, a kick-off meeting in Google Calendar and a Slack message to the team.
Put the goal into words. Add perspectives and timing right below.
Try it with a made-up agreement.
Sample agreement / fictional data
What the signature triggers.
- Trigger
- Agreement signed in Peak Sign.
- Flow
- “Client onboarding” starts with its tasks.
- Schůzka
- Kick-off in Google Calendar, Slack message to the team.
Your start in three answers
What should happen after the signature?
Fill in the example with a made-up order. You see which details Peak needs for the automation. Nothing is saved or created.
Local working example · nothing is saved or sent. Please don't enter personal data.
Three questions. A start without a gap.
Draft · not yet put together
- The trigger
- Still open
- The team
- Still open
- The start
- Still open
From the signature to day one
Trigger. Start. Inform.
The order makes sure the start doesn't depend on someone remembering.
- 01Trigger
The signature is the signal.
TriggerAgreement signed in Peak Sign.
Once the last signature is in Peak Sign, the automation starts once per agreement.
Peak Sign → trigger - 02Start
The flow takes over.
Flow“Client onboarding” starts with its tasks.
“Start a flow” creates the steps of your onboarding flow, and tasks go to the people in charge.
Flow → tasks - 03Inform
Team and calendar are in the know.
SchůzkaKick-off in Google Calendar, Slack message to the team.
Kick-off in Google Calendar and a Slack message through your connections. The history shows every run.
Sample artifact → kick-off meeting
The next proof is the product
Plan the next project start.
In Peak Automations you pick the trigger “agreement signed”, set flow, tasks, meeting and message, and switch on after the test run.
Start with Peak AutomationsPeak Automations / Your next step
Signature and start in one go.
Try the example with the next order that will be signed.
See the kick-off example
The start is already planned.
Kick-off in Google Calendar, Slack message to the team.
Frequently asked questions
Does the automation send contracts?
No. A person sends contracts in Peak Sign; the automation reacts to the completed signature.
What can happen after the signature?
Start a flow, create tasks, send a note, a Google Calendar event and a Slack message.
Does it run right after setup?
Only after a passed test run of the current version.