Estimated reading time: 5 minutes

Automations work this way:

  • Every time something happens in your Pipe

  • The automation will do something else in sequence.

You can set up an automation that creates the same Card in different pipes, and that connects with each other.

Their fields, assignees, emails, or connected database records will be the same and automatically updated in both pipes.

This automation works great for teams that need to update tasks, requests, payments, tickets (or any other type of activity) across different processes, without having to type in the same information twice.

Click here to read how teams can use this automation on their processes.

How to create new connected Cards?

First, choose an event for your automation.

That means choosing something that will happen in your pipe to create new connected cards in sequence.


✍️ Note: to access all connections in a pipe, click on Add connection.

As you click, you can view existing connections or add a connections that create cards in both pipes.


Some events trigger new connected cards:

  • When a card is created: every time a Card is created in pipe 1 → the same Card is created in pipe 2. The Card is a connection between pipes 1 and 2.

Connected card setup:

You can match fields that exist in pipe 1 and pipe 2 to update their information automatically.

Example: pipe 1 contains a field called "Employee's email" [1], and pipe 2 contains a field called "Email" [2].

Both fields are email field types that ask for a person's email address. It makes sense for those fields to be connected.

Set fixed value:

If you don't find corresponding fields, you can leave them blank.

Or, you can set a fixed value for all Cards: every time a connected Card is created, it will contain the same information.

  • When a card enters a phase: every time a Card enters a phase in pipe 1 → the automation creates a connected Card in pipe 2.

  • When a field is updated: every time a field is filled out in a pipe → a connected Card is created with the same information, in another pipe.

  • When all connected cards are moved to a phase: every time all connected Cards move to a specific phase, in a pipe → the automation created connected cards in another phase of another pipe.

  • When an alert is triggered: every time a Card receives a late, expired, or overdue alert → the automation creates a connected Card in another pipe.

  1. Late: the Card reached the maximum time for staying in a phase.

  2. Expired: the Card reached the maximum time for staying in any active phase of the entire pipe.

  3. Overdue: the Card exceeded its due date (red label).

  • When an email is received: every time a Card receives an email (in a specific phase of the process) → the automation creates another Card, in another pipe, with the same email history.

How teams use this automation?

Check some examples of how teams use this automation in their process and how you can use it in yours:

  • Finance: in a Purchasing process, every time an order moves from phase "To pay" to phase "Paid", a connected Card is created on the pipe Accounts Payable. The team assigned to collect invoices and receipts know exactly what was purchased, what's the amount, the requester's department, etc.

  • Human Resources: in Recruitment, every time a candidate replies the job offer email, a connected Card with their information is created in the Employee Onboarding pipe.

  • Customer Service & IT: in a Customer Support process (Customer Service), every time a request related to software bugs is moved to phase "Escalonation", a connected Card is created in pipe Bug Tracking (IT).

There are many more ways to utilize automation in your organization. If you want to know how to give the first steps, watch the video below:

Related articles:

How-to:

FAQ:

Did this answer your question?