Automations
Automate the running of pipelines with the power of automations.
Automations allow you to listen for specific events that happen in third-party integrations such as Gmail and Typeform and run pipelines based on triggers.
Let's say you have a pipeline you run which takes in an email and drafts a response for you. Through setting up an automation on the VectorShift platform, you can now have VectorShift automatically listen for new emails and draft replies as they come in.
The integrations VectorShift currently supports on the platform that have automation triggers includes:
Gmail
Linear
Typeform
Airtable
Notion
Github
Google Calendar
Google Drive
Google Sheet
Hubspot
Slack
Step 1: Choosing the integration and event to respond to
In the first step of creating an automation, you will select the event that the automation will respond to / which integration you want to associate with the automation (e.g., integration: Gmail; event: New Email).
On the "Automations" tab, click "New" >> "Create Automation".
Select the app you want to associate with the automation. Click "Connect" and go through the OAUTH flow.
Select from the available events to respond to. Here we select "New Email".
Click "Create Automation".
In this case, we are going to run a pipeline when a new email comes in.
Step 2: Choose Trigger
Give the automation a Name
Choose the trigger which in this case, means which inbox (e.g., inbox, spam, trash) within your Gmail should we listen for the event (new email) from step 1.
We will select inbox in this example, meaning we want a pipeline to run when a new email comes into my inbox.
Step 3: Choose a pipeline and match records
Choose a pipeline that you want to run when the event/trigger occurs.
Then, under "match records" drag the records to the input boxes. When the event occurs, the data from that record will be passed to the input node (and the pipeline will run accordingly).
A simple example is if you might want to build an automation that whenever you get an email in your inbox, print it out in Slack. This pipeline will have one input node where you will pass the body of the email. In this case, you will drag the "contents" record and match it to the input node in the pipeline.
Last updated