Skip to main content
Odoo connects to your own server, with an API key you create in Odoo — not a sign-in, and no app to install on the Odoo side. Tap works with Odoo 16, 17, 18, and 19, on Odoo Online or self-hosted.
Odoo only opens its external API on its Custom pricing plan. On a lower Odoo plan the connection cannot be made — that’s an Odoo limit, not a Tap one.

What syncs

A new record gets a title (Sara – Acme) plus the sales team, stage, and tags you picked when you connected.
An update never moves a record. If your team drags an opportunity to another stage, a later sync from Tap leaves it there. Team, stage, and tags are applied when the record is created and never again.
Meetings need Odoo’s Calendar app installed. Leads created in Odoo are not imported into Tap — no CRM connector does that.

Connect

1

Create an API key in Odoo

In Odoo: Preferences → Account Security → New API Key. Copy it — Odoo shows it once.The user you create the key for needs Sales access (Sales / User: All Documents) to write leads. With less, leads can still be saved as contacts.
2

Add the connection in Tap

Integrations → Odoo → Connect, then fill in:
  • Odoo address — your server, e.g. https://yourcompany.odoo.com
  • API key — the key you just copied
  • Login and Database — needed for Odoo 18 and earlier. On 19+ Tap works them out
Tap checks the connection against your server before storing anything, and works out which protocol your Odoo version needs on its own.
3

Choose what records look like

Pick whether leads become leads, opportunities, or contacts, and set the sales team, stage, and tags new records should get. Tap reads these from your database, so the options are your own.
4

Map your fields

See Field mapping. Your custom Odoo fields are included.
Tap never shows the key again after you save it — only its last four characters.

Sending leads already in Tap

Leads you captured before connecting Odoo don’t go there on their own. The connection page has a Leads already in Tap section for them: “Send leads captured before you connected. Leads already in Odoo are skipped.”
1

Send leads to Odoo

Press Send leads to Odoo. Progress reads Sending 120 of 480… and you can leave the page while it runs.
2

Read the result

When it finishes you see how many were sent, failed, and skipped — for example “352 sent · 0 failed · 128 skipped”. A line underneath, Already in Odoo: 128, counts the leads Tap knows Odoo already has.
A lead counts as already in Odoo if it reached Odoo any way at all — synced automatically, sent from this section before, or exported by hand from the Leads page. Those are skipped, so you can press the button again after a busy week without sending anything twice.

Send all again

Once you’ve made a run, Send all again appears next to it. It sends every lead, including the ones Odoo already has, after asking you to confirm: “Every lead goes to Odoo again. The ones it already has are updated, not added twice. It can take a few minutes.” Use it after you change your field mapping and want existing Odoo records refreshed. Records are matched the same way as any sync — see Duplicates — and updated under your mapping’s overwrite rules.
A lead someone typed straight into Odoo is unknown to Tap until a run matches it by email or phone. It’s updated rather than duplicated, but it’s counted as sent, not skipped.
Send all again is disabled while a run is in progress, and when the API key needs replacing.

Reopening a task

Moving a follow-up from Done back to To do or In progress in Tap reopens it in Odoo too:
  • Odoo 19 reopens the same activity.
  • Odoo 18 and earlier delete an activity when it’s marked done, so there’s nothing to reopen. Tap plans a new To-Do activity on the same record with the task’s text and due date. The old one stays in the chatter as a done message.

Connecting from the app

Personal accounts can connect Odoo from the mobile app too: Export to CRM → Odoo, then the Odoo URL, database, login email, and API key — “Tap sends your leads to Odoo as that user.” Its settings offer Test connection, Update API key, where leads go (CRM leads or contacts, lead or opportunity, sales team, stage, tags), and whether to assign the salesperson by email. See CRM in the app.

API keys expire

Odoo 19 will not issue a key that lasts longer than three months. Tap reads the expiry date from your server (Odoo 18 and up) and warns you 14 days ahead. On the day it expires, every sync stops and the connection reads Reconnect needed.
Reconnecting with a new key keeps everything — your settings, your field mapping, and the record links on existing leads. Put a reminder in your calendar two weeks before the key is due.

One connection, one server

Each connection carries its own address, database, login, and key. Different departments can point at different Odoo servers, and there’s no shared Odoo address across your account. Who can manage a connection depends on who owns it: a personal connection is managed by that member, a department’s by a full-team admin or that department’s admin, and the company’s by a full-team admin.

Duplicates

Odoo doesn’t enforce unique emails on a lead, so Tap looks before creating:
  • By email, case-insensitively — Sara@Acme.com finds sara@acme.com.
  • By phone, but only when the lead has no email at all. A phone is often a switchboard, and two colleagues sharing one are two different people.
  • Archived records count. A lead someone marked lost is still that person’s record.
When a match is found, Tap updates it instead of creating a second one, following your field mapping’s overwrite rules.

Notes specific to Odoo

A Tap note becomes an internal chatter message on the record. It’s never emailed to anyone. Editing the note in Tap corrects that message in place rather than adding a second one — see Notes.
Follow-ups are created as To-Do activities without Odoo’s “assigned to you” email, so syncing a day of leads doesn’t flood anyone’s inbox.
Check the address is reachable from the internet and includes https://. A self-hosted server behind a VPN or an IP allowlist can’t be reached by Tap.
The key is wrong, expired, or belongs to a user who has been deactivated. Create a new key and reconnect.
Tap matches the capturing member’s Tap email to an Odoo user’s email. No match means Odoo’s default owner.
Disconnecting deletes the connection and the stored key. Your field mapping is kept for when you reconnect, and nothing already synced is removed from Odoo.

Not arriving?

Work through the troubleshooting guide.