What is Integromat?
Integromat (now called Make) is a powerful tool for building automations, connecting apps, and building better workflows. You can use Integromat to connect Attio to thousands of platforms and services and move data between them automatically.
What is a scenario?
A scenario in Integromat (similar to a Zap in Zapier) is an automation workflow designed to connect apps. Scenarios are made up of a trigger and one or more actions that fundamentally say "When this happens, do that." You can pick from pre-made template scenarios, or build one yourself.
In order to build automations with Integromat, you’ll first have to connect your favorite apps and services. This means giving Integromat permission to send and receive data between platforms. Learn more about connecting to apps.
Note: To connect Attio to Integromat, you’ll first need to generate an API key - we recommend setting all of the permissions to Read and Write to help your automations run smoothly.
Triggers and actions
A trigger kicks off your scenario, initiating one or more actions. For example, you might build a simple scenario that automatically sends all new leads in Facebook Lead Ads to a database in Google Sheets. In this case, the creation of a new lead in Facebook Lead Ads would be your trigger, while the adding of a new row in Google Sheets would be the action. In Integromat, that scenario would look like this:
Adding modules and filters
Each new step in your automation workflow is called a module, and you can add as many as you like by clicking on the semicircle to the right of your connected app. Click on a module to make changes and add your criteria.
Create filters for your action by clicking on the semicircle to the left of your connected app. Filters allow you to set rules that ensure your scenario only runs under certain conditions. For the Facebook Lead Ads example, you might want to set a filter that prevents the scenario from running if the company name already exists in your Google Sheet. Learn more about filters in Integromat.
When configuring modules in Integromat, you’ll need to specify which data should be sent from one app to another - this is called mapping. It might be name or email address, the company someone works for, or the date they submitted a form for example.
In the example above, we’ve chosen the value 1. Field data: Company name from the dropdown. The dropdown contains all the data points collected by our Attio trigger, and allows us to pick and choose which fields will be used. Learn more about mapping.
To trigger automations with Attio, you'll need the Watch Entries trigger. This trigger watches your selected Attio collection for any new entries or changes to their attributes. Once one of these conditions is met, your scenario will run.
Integromat can use other apps to trigger certain actions in Attio. From creating a new collection to updating an entry's attributes, there are over 20 possible Attio actions to choose from in Integromat. Popular triggers are:
- Create a Collection
- Update a Collection Attribute
- Assert a Person/Company
- Create an Entry
- Update an Entry
Assert means to ‘create if not already there’. If the person or company already exists in your Attio collection, Integromat will return this record.
Ordering your Attio modules
Scenarios in Integromat work a lot like flow charts, so it's important to order your steps correctly. If you're creating or updating entries in Attio with Integromat, the order below should serve as a guide to ensure your scenarios work as expected.
- Assert a Person/Company or Get a Person/Company
- Create or Get an Entry
- Update an Entry
In Attio, an entry is a reference to a record in a collection. You'll always need to first get or assert a person/company before you create a new entry.
There are lots of useful guides in the Integromat help center, but these are some of the most useful ones to refer to when building scenarios with Attio: