History, connections, versions, and settings
Get insights into workflow data such as transaction report, a list of app connections, and the version history with the name of a modifier contributing to the created automation.
A smooth creation of a journey comprises integrating apps, establishing connections, and monitoring the execution each time a trigger and action sends and receives the data, respectively. While monitoring, a trail of successful execution or failure highlights the nature of a journey's response to the data flow. With the help of these insights, you can map the I/O data and figure out the variables (data pills) used. As a result, you'll get a better idea about how your journey is executing and its reliability to automate the tasks.
In this document, we will take a look at the history, connections, and versions of a journey.
Use case
Fetch a new email in Gmail and send a copy of it to another email via Gmail.
- Trigger: Gmail-Get email
- Action: Gmail - Send email
Prerequisites
Before configuring a journey, create a Google Workspace account to have an official Gmail account ready to implement the use case.
Updated about 2 years ago