Automation platforms

Make integration

The arteemis app for Make starts a scenario when something happens in arteemis, and lets any scenario act in arteemis: create or update contacts, fill lists, enroll contacts in campaigns, move them in the pipeline, open tasks, or call any tool of the arteemis API. It connects with a key of your arteemis workspace.

Read the API guide Contact support

What it does

Triggers

Watch new replies: a contact replied by email or on LinkedIn.
Watch contact status changes: new, in campaign, paused, replied (with the kind of reply), client or do not contact.
Watch leads entering campaigns and Watch leads leaving campaigns (with the reason).
Watch sent messages: an email, a LinkedIn message or a LinkedIn invitation left.
Watch accepted invitations: an invitation sent by a campaign was accepted.
Watch new tasks: a reply to answer, a call, a to-do or a message waiting for approval.
Watch pipeline stage changes.

Actions and search

Create or update a contact: matched on email, then LinkedIn profile, optionally into a list.
Add a contact to a list.
Enroll a contact in a campaign.
Add or move a contact in the pipeline.
Create a task.
Search contacts: by email or LinkedIn profile URL.
Make an API call: any tool of the arteemis API.

Each trigger registers its own webhook in arteemis when you create it in a scenario, and removes it when you delete the webhook. Events arrive within a minute.

Requirements

A Make account.
A workspace key of arteemis, made by an owner or admin in Settings > MCP & API. A member's personal token also works for actions, with their own role; triggers need a workspace key or the admin role.
A free webhook slot: a workspace holds 50 webhooks, and each trigger uses one.

Set it up

Make a workspace key

1Sign in to arteemis and open Settings > MCP & API.
2Under the API, name a key and choose Create key. Copy it at once: it is shown only once. It starts with art_key_.

Connect in Make

1In a Make scenario, add an arteemis module.
2Create a connection and paste the key as its API key.
3For a trigger, create its webhook: arteemis registers it at once. Pick lists, campaigns and stages in the dropdowns, then run the scenario once to check it.

Data exchanged

Data	Direction	Details
Events	arteemis to Make	The trigger's event: the contact (name, email address, LinkedIn profile, job title, company, status, custom fields) and, as the event has them, the message, campaign, enrollment, task or stage.
Search results and API answers	arteemis to Make	The contact found, or what the called tool answers.
Dropdowns	arteemis to Make	Names of your lists, campaigns and pipeline stages.
Contacts	Make to arteemis	Created or updated by the modules: name, email, LinkedIn profile, company, custom fields.
Lists, campaigns, pipeline, tasks	Make to arteemis	A contact added to a list, enrolled in a campaign, added or moved in the pipeline; a task opened.
Webhooks	Make to arteemis	The address Make gives each trigger, kept until its webhook is deleted.

Disconnect

Delete a trigger's webhook in Make: it is removed from arteemis.
To cut every access at once, revoke the key in Settings > MCP & API: every call made with it is then refused.
arteemis keeps nothing of Make besides the webhook addresses of its triggers.

Troubleshooting

A trigger cannot be created: it needs the admin role: The key is a personal token of a member who is not an admin. Use a workspace key.
A trigger cannot be created: limit reached: Your workspace already holds 50 webhooks. Delete the webhooks you no longer use.
Events arrive a minute late: arteemis sends its webhooks once a minute. A delivery that fails is retried for about 21 hours.
Search contacts returns one contact: It answers the best match only, by email or LinkedIn profile URL.

Support

romain@arteemis.xyz

A question about this integration, or something that does not work as described here: write to us. You get an answer within one business day, in French or English.

Send an email