A CRM or other software

Business software rarely has an Azimea integration of its own, and it does not need one. Most of it can do at least one of three things, and each one is a way in.

The software can	Way in	What you get
Export a list (CSV or Excel)	Import the file	Its people, as contacts, with their fields and consent
Call a URL when something happens (webhook, automation, workflow rule)	A flow’s trigger URL, directly or through Zapier, Make or n8n	A flow that starts the moment something happens there
Send emails through an SMTP server	The Azimea SMTP relay	Its own emails, from your domain, tracked in Azimea

Import an export

1. In the software, export the people you want to write to, with their email address and the fields you will use (a plan, a status, a date, a city).
2. In Azimea, Contacts › Import contacts: choose the file, map each column to a field (or create the field there), and say whether you may send them marketing. Every step is described in Importing a file.
3. Build segments on those fields and send campaigns to them.

Keep it current by importing again. The same email address is updated, never duplicated: newer values replace older ones, an empty cell never erases a known value, and consent only moves up. Export and import again whenever the list changes; nothing has to be cleaned up first.

A file brings people and their fields, not what they did: for a flow that reacts as things happen, use one of the two ways below.

Let the software start a flow

If the software can call a URL when something happens (often called a webhook, an automation, a workflow rule or a notification to a URL), it can start an Azimea flow directly:

1. In Flows, create a flow with API as its trigger, generate its token and publish it.
2. In the software, set the URL to the flow’s Trigger URL, the method to POST, add the header Authorization: Bearer azm_wf_…, and send a JSON body with at least email.

The full body is in Start one flow from outside. If the software cannot add a header or shape the body, put Zapier, Make or n8n in between: the software notifies the tool, the tool calls Azimea. See Zapier, Make and n8n.

Send its emails through Azimea

Software that sends its own emails (confirmations, reminders, invoices, password resets) usually has an SMTP setting. Point it at Azimea:

Setting	Value
Server	smtp.azimea.com
Port	587 with STARTTLS, or 465 with SSL/TLS
Username	azimea
Password	An API key with the Send transactional emails permission

The sender address in the software must be on your verified domain. The emails then appear in Azimea with their delivery statuses. These are transactional emails only: newsletters go through campaigns, with their consent rules. The full guide, with the answers you may see, is Send through SMTP.

Troubleshooting

Symptom	Likely cause	Fix
Rows were not imported	The import result lists each line and its problem, usually an invalid address.	Fix those lines in the file and import it again.
A contact from the software gets no campaigns	The file was imported as Not yet.	Import again with the right choice, only if you hold their consent.
The software’s call to the trigger URL is refused	The token or the header is wrong, or the flow is not published.	See the table in Zapier, Make and n8n.
The software cannot sign in to SMTP	The password is not an API key, or the key lacks the sending permission.	Use a key with Send transactional emails. More answers in Send through SMTP.

Related

• Contacts and imports
• Segments
• Send through SMTP
• Your own application