Structure of a Journey
This section explains the structure of a Journey in Quickwork, focusing on how workflows are logically organized with triggers and steps to automate tasks across different applications.
What is a Journey
A Journey in Quickwork is nothing but an automated workflow (a set of logically connected steps designed to automate a task). For example, creating a new task in JIRA and sending its details via email using Gmail is a Journey.
Journeys can be simple or complex, depending on the use case and the apps involved. Once you have configured and activated a Journey, Quickwork automatically executes it each time the specified trigger event occurs. A few practical examples of Journeys are:
- When a new task is created in the Google Tasks account, translate the note into Spanish (using Google Translate) and send the translated text to Microsoft Outlook.
- When a Slack channel receives messages, if the message contains specific keywords, convert them into Trello cards to streamline task management.
- Automatically add new Shopify customers to a Mailchimp mailing list for efficient email marketing campaigns.
Consider a use case wherein a company receives customer feedback through various channels like online forms, emails, or manual entries. To manage this feedback efficiently, they need a streamlined process that ensures all issues and comments are promptly addressed by the customer support team.
This can be achieved by creating a Journey where each customer feedback entry in a Google Sheets spreadsheet automatically generates a support ticket in Freshdesk. The automation ensures that no feedback is overlooked and all customer concerns are addressed on time.
📚Additional resources
Triggers to initiate Journeys
Configuring actions
Establishing connections
Building your first Journey
Updated about 1 month ago