No code: Zapier, Make, n8n
Get every reply or accepted invitation in your tools, and add prospects, without writing a program.
Two building blocks are enough, and every automation tool knows them:
- a webhook to receive Lidmeo's events (a reply, an accepted invitation…);
- an HTTP call with an API key to act on Lidmeo (add a prospect, set a stage, write a note).
Lidmeo apps for Zapier, Make and n8n are coming: until then, these two building blocks already do everything.
Receiving an event
In your tool, create a trigger that receives a webhook: Webhooks by Zapier ("Catch Hook") in Zapier, the Webhooks module ("Custom webhook") in Make, the Webhook node in n8n. Copy the address it gives you.
In Lidmeo, open Assistant IA et intégrations (AI assistant and integrations, in the Réglages menu), then Pour les développeurs (for developers), Webhooks section, and Ajouter une adresse de réception (add an endpoint). Paste the address and choose the events, for example prospect.replied and invitation.accepted. An endpoint added this way receives everything your account reads, contact details and message texts included.
Click Lidmeo's Envoyer un essai (send a test) button: your tool receives a sample prospect.created, which teaches it the shape of the data. For the exact shape of another type, call POST /v1/webhook_endpoints/{id}/test with { "type": "…" }. Build the rest of your scenario.
Each delivery contains the whole event: its type, and in data.object the object it is about, as it was when the event was recorded. For prospect.replied and invitation.accepted, it is the prospect, with their name, company, LinkedIn link and stage. The event catalog is here.
Your tool's address is a secret
A no-code tool does not always verify the signature of deliveries. Its receiving address contains a random token: never publish it. With n8n or Make, you can verify the signature in a code step, as explained in verifying a signature.
Acting on Lidmeo
Create an API key in Lidmeo (Assistant IA et intégrations, Pour les développeurs), then use your tool's HTTP module (Webhooks by Zapier, "Custom Request" action; HTTP in Make; HTTP Request in n8n):
- address:
https://api.lidmeo.com/v1/…; Authorizationheader:Bearer lid_live_…;Content-Typeheader:application/json.
Four recipes
Every reply in Slack
prospect.replied event → a Slack message with data.object.full_name, data.object.company.name and the link data.object.linkedin_url. It is a prospect's first reply, all channels together: one alert per person.
Every accepted connection in your CRM
invitation.accepted event → create or update the contact in your CRM. Then give the contact's id back to Lidmeo, so the two stay linked:
PUT https://api.lidmeo.com/v1/prospects/pros_…/external_ids
Content-Type: application/json
{ "hubspot": "12345" }A prospect from your form into Lidmeo
Your form or your file → PUT /v1/prospects with match_on: "linkedin_url": the prospect is added to your Lidmeo CRM, or completed if it is already there (never twice). A prospect already there only gains the fields it does not have: nothing is overwritten, it keeps its place in a campaign, and a removed prospect stays removed. Nothing is sent to them.
{
"match_on": "linkedin_url",
"linkedin_url": "https://www.linkedin.com/in/claire-durand",
"first_name": "Claire",
"last_name": "Durand",
"company": "Nova Conseil",
"email": "claire@nova-conseil.fr"
}Unsubscribes everywhere
prospect.opted_out event → mark the person "do not contact" in your CRM and your e-mailing tools. It is an obligation, see your obligations.