Automation platforms

Zapier integration

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

What it does

Triggers

  • New Reply: a contact replied by email or on LinkedIn.
  • Contact Status Changed: new, in campaign, paused, replied (with the kind of reply), client or do not contact.
  • Lead Entered Campaign and Lead Left Campaign (with the reason).
  • Message Sent: an email, a LinkedIn message or a LinkedIn invitation left.
  • LinkedIn Invitation Accepted: an invitation sent by a campaign was accepted.
  • New Task: a reply to answer, a call, a to-do or a message waiting for approval.
  • Pipeline Stage Changed.

Actions and search

  • Create or Update Contact: matched on email, then LinkedIn profile; optional company, list and custom fields.
  • Add Contact to List.
  • Enroll Contact in Campaign.
  • Add or Move Contact in Pipeline.
  • Create Task: a call or a to-do.
  • Find Contact: by email or LinkedIn profile URL, one contact at most.

Each trigger creates its own webhook in arteemis when the Zap is switched on, and deletes it when the Zap is switched off. arteemis signs each delivery and posts it within a minute of the event.

Requirements

  • A Zapier 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 switched-on trigger uses one.

Set it up

Make a workspace key

  1. 1Sign in to arteemis and open Settings > MCP & API.
  2. 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 Zapier

  1. 1In Zapier, create a Zap and choose arteemis as the trigger or action app.
  2. 2When Zapier asks to sign in to arteemis, paste the key in API Key. The connection takes the name of your workspace.
  3. 3Pick the trigger or action, fill its fields (lists, campaigns and stages are offered in dropdowns), test it and publish the Zap.

Data exchanged

DataDirectionDetails
Eventsarteemis to ZapierThe 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 resultsarteemis to ZapierThe contact found, with its details.
Dropdownsarteemis to ZapierNames of your lists, campaigns and pipeline stages.
ContactsZapier to arteemisCreated or updated by the actions: name, email, LinkedIn profile, company, custom fields.
Lists, campaigns, pipeline, tasksZapier to arteemisA contact added to a list, enrolled in a campaign, added or moved in the pipeline; a task opened.
WebhooksZapier to arteemisThe address Zapier gives each trigger, kept while the Zap is on.

Disconnect

  • Switch a Zap off, or delete it: its webhook is deleted in 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 Zapier besides the webhook addresses of the Zaps that are on.

Troubleshooting

A trigger cannot be switched on: 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 switched on: limit reached
Your workspace already holds 50 webhooks. Switch off the Zaps and other 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.
Zapier answers 401
The key was revoked or mistyped. Make a new one and reconnect the account in Zapier.

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