How do I connect Odoo to Flunter?

From Settings > CRM, your admin enters your Odoo instance URL, login and API key. No developer needed.

Which Odoo lists can I call?

Saved filters on your Odoo contacts. Each filter becomes a calling campaign. There's no owner filter on import: to give each rep their own book, filter by salesperson in Odoo before saving the filter.

How do calls show up in Odoo?

Each finished call is posted as a note in the contact's chatter, with the campaign, the outcome, the rep, the numbers, the AI summary and the recording link.

Are call outcomes mapped to Odoo values?

No. The call outcome is written as text in the chatter note, but it isn't mapped to an Odoo value.

Do activities scheduled in Odoo show up in Flunter?

No. Tasks created in Flunter are pushed to Odoo as scheduled activities, but not the other way around. The contact's Odoo history stays visible in Flunter during the call.

Your whole business runs on Odoo. Now your calls do too.

Turn an Odoo contact filter into a call session: every call lands in the contact's chatter, with its outcome, AI summary and recording.

Try it free

Book a demo

Odoo and Flunter, connected in three steps

No CSV exports between Odoo and your dialer.

Connect Odoo
In Settings > CRM, your admin enters your Odoo instance URL, login and API key, then maps the contact fields.
Import a filter
Pick a saved filter on your Odoo contacts. Flunter turns it into a calling campaign, ready for the parallel dialer.
Dial, the chatter keeps up
After each call, Flunter posts a note in the contact's chatter, with the outcome, the AI summary and the recording link.

What flows between Flunter and Odoo

Import saved filters	On contacts
Filter by owner on import	No, filter inside Odoo
Call logged in the chatter	Note on the contact
Call outcome mapping	Outcome written in the note
Call recording	Recording link
AI conversation summary	In the call note
Flunter notes pushed to Odoo
Flunter tasks to Odoo	As Odoo activities
Odoo scheduled activities in Flunter	No, they stay in Odoo
Contact field mapping
CRM history shown in Flunter
Full transcript	No, available in Flunter

Your Odoo filters become your call lists

When your CRM, quotes and invoicing all live in Odoo, your prospecting lists are already there. Customers with no order in six months, prospects in one region, contacts from a trade show: you've filtered and saved them in Odoo.

Flunter imports those saved filters on your contacts and turns them into calling campaigns. The parallel dialer works the list up to 5 numbers at a time. As soon as a human picks up, the rep is live with the record on screen.

Import from a saved filter on contacts
Contact fields mapped by the admin
Up to 5 simultaneous calls

Every call lands in the chatter

In Odoo, a contact's history lives in the chatter. Flunter posts a note there after every finished call, without the rep ever opening Odoo.

The note includes the campaign, the call outcome, the rep, the caller and called numbers, the AI summary of the conversation and the recording link. Whether it's a rep taking over the account, the accountant chasing an invoice or the founder prepping a meeting, everyone sees the last conversation.

One chatter note per finished call
AI summary and recording link
Admin picks which call statuses sync

Notes and follow-ups pushed to Odoo

Notes taken in Flunter are pushed to Odoo. Follow-up tasks created in Flunter become scheduled activities on the contact. Whatever gets decided on the phone is available to the whole team, in the tool they use every day.

Good to know: tasks sync one way, from Flunter to Odoo. Activities scheduled in Odoo don't come back into Flunter. Call outcomes aren't mapped to Odoo values either: they're written in the note, readable by everyone.

Flunter notes pushed to Odoo
Flunter tasks created as Odoo activities
The contact's Odoo history visible in Flunter

Ultimate frisbee player making a diving catch

Other integrations

HubSpotImport HubSpot lists, log calls as native Call objects with owner and disposition, and see HubSpot tasks inside Flunter.See the integration
SalesforceImport Campaigns (Contacts and Leads), log calls as Call-type Tasks, and handle Lead to Contact conversion.See the integration
PipedriveImport filters on persons and leads, log calls as Call logs with the audio file attached.See the integration
CloseImport your saved searches, log calls as Call activities on the lead, and sync tasks both ways.See the integration
Boond ManagerImport from a Boond URL (contacts, actions, opportunities) and log every call as a Boond action.See the integration

Frequently asked questions

From Settings > CRM, your admin enters your Odoo instance URL, login and API key. No developer needed.
Saved filters on your Odoo contacts. Each filter becomes a calling campaign. There's no owner filter on import: to give each rep their own book, filter by salesperson in Odoo before saving the filter.
Each finished call is posted as a note in the contact's chatter, with the campaign, the outcome, the rep, the numbers, the AI summary and the recording link.
No. The call outcome is written as text in the chatter note, but it isn't mapped to an Odoo value.
No. Tasks created in Flunter are pushed to Odoo as scheduled activities, but not the other way around. The contact's Odoo history stays visible in Flunter during the call.