The final thing to do is starting the Trigger. By default, Triggers are in a ‘paused’ state when you first add them. This is to avoid that runs are started for the playbook while you’re still building it.
<aside> 👷 Do it yourself: Start the trigger by clicking the ‘Start trigger’ button within the Trigger section
</aside>
Unpause the Trigger by clicking the ‘Start trigger’ button
And finally, let’s test our playbook! This is as simple as submitting an entry in the Google Form we created early on. Soon after, you should see a run for this playbook appear on your dashboard! 🎉
If you’re bumping into issues or have any questions, don’t hesitate to reach out to us via [email protected] – we respond to every email!
<aside> 👷 Do it yourself: Submit an entry in the client signup Google Form you created earlier on in this tutorial
</aside>
Animation of an end-to-end test run of the client onboarding playbook. A run is automatically triggered after a new client submits an entry in the Google Form
<aside> 💡 Most Triggers will trigger on updates in another app within a minute. There are a few that will check every hour. You can always force-refresh a trigger when testing by clicking the refresh icon 🔄 that shows up whenever a trigger is referenced
</aside>
When you go to Relay, you’ll land on the main dashboard. This dashboard contains an overview of all playbooks in your workspace, and shows current (active) and completed runs for each.
The main dashboard of Relay