Integrations

The Integrations section of the admin dashboard (under Connections, headed "Chat bots") connects your community to the chat tools your members already use. CRMs are synced from the Import & sync section (under Community), which this page also describes below, and event platforms (Luma, Eventbrite, HelloAsso) are connected from the Events section.

Chat bots

Telegram and WhatsApp bots are linked by each member from their own Settings → Integrations, not from the community console — see Chat bots.

CRM sync

In the Import & sync section, under Sync a CRM, each CRM provider has a card. Set up sync for a provider, then open its Sync and history page, Edit mapping, or Disconnect it; an expired connection offers Reconnect. The card shows Connected, Not connected, or Expired, when it last synced, and its sync history. Disconnecting removes the saved token; profiles already synced are not deleted. The people menu's Sync with CRM opens the same section, and a sync opened from it comes back to it when it ends.

Saved credentials reach only the source they were saved with: an Airtable token its base and table (the sync offers no other, and says so beside a Reconnect button), a HelloAsso API client its organization, Odoo credentials their instance and database. To sync from another source, reconnect with credentials for it.

Keep the page open while a sync fetches the records from the CRM. Once they are fetched, the import runs on our servers: you can leave the page, and the result appears in the card's sync history. When the sync ends, whoever started it is told by push and by email, as their notification switches allow, if they still administer the community (see Notifications). Disconnect while a sync is still importing stops that import: a batch already running finishes its own records, no further batch starts, and the records already imported are kept.

Records of one sync that describe the same person become one profile: two that share an email address and whose names agree (one has no name, or every word of the shorter name is in the longer one), or two matched to the same existing member. The extra record fills the profile's empty fields, except the location (city, region and country), which it brings whole and only when the profile has no part of one, and is counted as skipped. People who share an address but not a name, such as a family address, stay apart. One sync keeps track of at most 50 different people per address: past that, as on a shared box such as info@, a further person on it is not tracked under that address, so a later record of theirs can become a second profile.

For Odoo, Which partners to import offers Contacts (people), Companies or All partners, and Only partners with an email address narrows any of them. None of them imports a contact's invoice or delivery addresses, as long as the account you connected with can read the partner's address type: on an instance that hides that field from it, Contacts (people) and All partners import those addresses as people too. For HelloAsso, an order that was cancelled or whose payments were all refunded in full is not imported, and Also import forms of these types created later (offered once you have selected forms) brings in, at the next sync, the people of forms created after you saved the selection, such as next season's membership form.

Synced people arrive as community profiles, with their source recorded so that later enrichment keeps CRM-provided fields; on a profile nobody has claimed, LinkedIn's details are combined with them rather than replacing them (see Enrichment).

The field mapping can also send a column into one of your community's custom fields, or create a new field there. A new field's type is proposed from the column, and you can change it: an Airtable column proposes its own Airtable type where one matches (a single select brings its list of choices), and other columns a type guessed from their values.