LidmeoDevelopers

Your CRM: HubSpot, Pipedrive and others

Keeping your CRM up to date with Lidmeo: the rules that work, until the built-in syncs arrive.

Built-in syncs with HubSpot and Pipedrive are coming. You can already connect any CRM with webhooks and the API, following the same rules they will follow.

The rules of a good sync

1. Enter the CRM on acceptance. A prospect proposed by Lidmeo is only a lead so far. Create the contact on invitation.accepted: it is the moment the person becomes a connection. For your imported prospects, prospect.created is enough.

2. Link the two records. Give your CRM's id back to Lidmeo with PUT /v1/prospects/{id}/external_ids. It then comes back in every prospect (external_ids) and every event: you always know which contact to update, without searching by name. A contact created in your CRM enters Lidmeo through PUT /v1/prospects: a prospect already there is only completed (its empty fields), it keeps its place in a campaign, and a removed prospect stays removed. A prospect already linked to another object of the same tool answers 409 conflict, with linked_external_id: change that link with PUT /v1/prospects/{id}/external_ids.

{ "hubspot": { "id": "12345", "url": "https://app.hubspot.com/contacts/1/record/0-1/12345" } }

3. Follow the conversation. prospect.replied (the first reply) and message.received (each message, text included) move the deal forward. message.sent tells each message that left, with its channel (linkedin or email) and its kind (first_message, follow_up, reply).

4. Write into Lidmeo what happens in the CRM. A call, a meeting, a note: POST /v1/prospects/{id}/notes with kind (call, meeting, email, task, note) and your external_id, which prevents any duplicate if you send the same note again. An external_id already used by a note of another prospect answers 409 conflict, and nothing is moved. A deal won or lost: PATCH /v1/prospects/{id} with crm_stage.

5. Propagate "do not contact". prospect.opted_out must mark the contact everywhere. The other way, an unsubscribe coming from your CRM enters Lidmeo through POST /v1/suppressions: nothing leaves for that person anymore, on any channel.

6. Catch up rather than reread everything. For a first sync, go through GET /v1/prospects page by page, while has_more is true (a page can be short, even empty, without being the last). Then follow the events, or reread only what changed with updated_since. On prospects, it follows changes of the prospect record itself: adding or removing a list, linking an external id or renaming a stage does not bring it back. On conversations, it follows the last message. It combines neither with a view nor with the search (400 invalid_request). See pagination.

Contact details

The e-mails and phone numbers found by Lidmeo only go out with the contacts:read scope, on the key or on the webhook endpoint. Copy them into your CRM only if you need them: see your obligations.

On this page