Odoo CRM Integration Issues – Sales Team/Company Fields & Missing Facebook Lead Triggers

Hello everyone,

I am currently building a Facebook Lead Ads → Odoo CRM automation using Pabbly Connect and I'm facing two major issues.

Issue 1: Odoo Sales Team and Company Fields

• Sales Team
• Company

• The Odoo record ID (integer value)
• The Sales Team name
• The Company name

However, when I use the same values in an Update Record step:

• Sometimes the step completes successfully.
• Sometimes the field is not updated in Odoo.
• Sometimes the step shows success, but when I open the detailed response, Odoo returns an internal error.

Error Message:

Odoo Server Error

Error Data:

builtins.TypeError
'NoneType' object is not iterable

Screenshot attached below.

My questions are:

1. What is the correct format expected by Odoo for:
   
   • Sales Team (team_id)
   • Company (company_id)
2. Should these fields be sent as:
   
   • Integer ID
   • Record name
   • External ID
   • Another format
3. Has anyone successfully assigned Sales Team and Company through the Odoo connector?
4. Is there a known issue with Odoo Many2One fields in Pabbly Connect?

Issue 2: Missing Facebook Lead Ad Triggers

Example:

Lead 1: 8:00 AM → Triggered successfully

Lead 2: 8:05 AM → Not triggered at all

Lead 3: 8:10 AM → Triggered successfully

The middle lead is completely skipped and never enters the workflow.

This has happened multiple times.

My questions are:

1. Why are some Facebook leads not triggering even though they exist in Meta Lead Center?
2. Is there a delay issue with the Facebook Lead Ads trigger?
3. Is there any way to re-fetch or recover missed leads?
4. Has anyone experienced random missing lead triggers with Facebook Lead Ads?

Thank you.

Attaching File for

Odoo Sales Team and Company Fields

Hey @aniketnborhade,

Thank you for reaching out and for sharing the detailed information regarding both issues.

After reviewing your workflow and task history, we can see that the Odoo Create Record and Update Record actions are currently executing successfully. We were unable to locate the specific error shown in the screenshot within the recent task history records.

Regarding the error:

"Odoo Server Error - builtins.TypeError: 'NoneType' object is not iterable"

this appears to be an Odoo-side validation error. In most cases, such errors occur when the data passed to one of the mapped fields is not in the format expected by Odoo. Since the actions are working successfully at present, we are unable to identify the exact field that may have caused the issue earlier.

For the Sales Team (team_id) and Company (company_id) fields, you should pass the numeric Odoo record IDs. These IDs can be obtained directly from your Odoo account. Whether a field can be populated during record creation depends on the specific Odoo model and the fields supported by that record type.

At the moment, we are not aware of any known issues with Odoo Many2One fields in Pabbly Connect. If you encounter the error again, please share a task history where the error is visible so that we can investigate the exact cause.

Regarding the Facebook Lead Ads trigger issue, thank you for providing the lead timestamps. However, we would need a few more details to investigate further:

• The exact lead details that are visible in your Meta Lead Center but missing from Pabbly Connect.
• The timezone of the timestamps you shared (IST, UTC, etc.).
• Any identifying information for the missed lead, if available.

In some cases, we have observed that a lead may appear in the Meta Lead Center but is not returned through Meta's API. When that happens, the lead cannot be captured by the trigger. To determine whether that is the case here, we will need the details of the missed lead for verification.

As an alternative, you can use the "Retrieve Leads" action in Facebook Lead Ads to fetch leads from a specific form if you need to recover or verify lead data.

Once you share the missing lead details, we will be happy to investigate further and provide a more specific explanation.

Hi Team,

Thank you for your detailed response and for reviewing both issues.

Regarding the Odoo issue, I understand that the recent tasks are executing successfully. However, the concern is that the same values being used in the Update Record action work correctly, while the Create Record action throws the error:

"builtins.TypeError: 'NoneType' object is not iterable"

Specifically, I tested both the numeric IDs and the field names for the Sales Team (team_id) and Company (company_id) fields, but the Create Record action continues to return the error. Since the values are valid and accepted during updates, could you please confirm whether there are any known limitations or formatting requirements for these fields specifically during record creation?

For the Facebook Lead Ads issue, I will share the details of the missing leads, including the lead information visible in Meta Lead Center, timestamps, and timezone (IST), so that you can verify whether the leads were returned by Meta's API.

One additional concern is that we have observed multiple instances where leads visible in Meta Lead Center were not received by the instant trigger in Pabbly Connect. Since this directly impacts lead capture and follow-up, we would appreciate a more detailed investigation into whether there are any known limitations, API sync issues, or trigger reliability concerns that could cause this behavior.

I will provide the requested lead details shortly for further analysis.
Lead List from Meta:
[TABLE]
[TR]
[TD]id[/TD]
[TD]created_time[/TD]
[TD]ad_id[/TD]
[TD]ad_name[/TD]
[TD]adset_id[/TD]
[TD]adset_name[/TD]
[TD]campaign_id[/TD]
[TD]campaign_name[/TD]
[TD]form_id[/TD]
[TD]form_name[/TD]
[TD]is_organic[/TD]
[TD]platform[/TD]
[TD]how_old_is_your_child?[/TD]
[TD]which_school_does_your_child_attend?[/TD]
[TD]email[/TD]
[TD]full_name[/TD]
[TD]phone[/TD]
[TD]inbox_url[/TD]
[TD]lead_status[/TD]
[/TR]
[TR]
[TD]l:1310448687859718[/TD]
[TD]2026-05-30T19:19:47+05:30[/TD]
[TD]ag:120243937264420567[/TD]
[TD]AH_OIC-HK26-22A[/TD]
[TD]as:120243937264410567[/TD]
[TD]AH_OIC-HK26-22A[/TD]
[TD]c:120243937264430567[/TD]
[TD]AH_OIC-HK26-22[/TD]
[TD]f:2459462054516969[/TD]
[TD]OIC: Summer 2026 - Hong Kong- 30th May 2026[/TD]
[TD]FALSE[/TD]
[TD]fb[/TD]
[TD]33[/TD]
[TD]MITT[/TD]
[TD][email][email hidden][/email][/TD]
[TD]Aniket Borhade AHT[/TD]
[TD]p:+918087766444[/TD]
[TD]https://business.facebook.com/latest/6166740120009754?nav_ref=thread_view_by_psid[/TD]
[TD]complete[/TD]
[/TR]
[TR]
[TD]l:2034359637153087[/TD]
[TD]2026-05-30T18:33:00+05:30[/TD]
[TD]ag:120243937264420567[/TD]
[TD]AH_OIC-HK26-22A[/TD]
[TD]as:120243937264410567[/TD]
[TD]AH_OIC-HK26-22A[/TD]
[TD]c:120243937264430567[/TD]
[TD]AH_OIC-HK26-22[/TD]
[TD]f:2459462054516969[/TD]
[TD]OIC: Summer 2026 - Hong Kong- 30th May 2026[/TD]
[TD]FALSE[/TD]
[TD]fb[/TD]
[TD]12[/TD]
[TD]AHT[/TD]
[TD][email][email hidden][/email][/TD]
[TD]Sithessh20-AHT[/TD]
[TD]p:+9190566411183[/TD]
[TD]https://business.facebook.com/latest/5833216140051329?nav_ref=thread_view_by_psid[/TD]
[TD]complete[/TD]
[/TR]
[TR]
[TD]l:1914458325935055[/TD]
[TD]2026-05-30T18:23:51+05:30[/TD]
[TD]ag:120243937264420567[/TD]
[TD]AH_OIC-HK26-22A[/TD]
[TD]as:120243937264410567[/TD]
[TD]AH_OIC-HK26-22A[/TD]
[TD]c:120243937264430567[/TD]
[TD]AH_OIC-HK26-22[/TD]
[TD]f:2459462054516969[/TD]
[TD]OIC: Summer 2026 - Hong Kong- 30th May 2026[/TD]
[TD]FALSE[/TD]
[TD]fb[/TD]
[TD]12[/TD]
[TD]AHT[/TD]
[TD][email][email hidden][/email][/TD]
[TD]Sithessh19-AHT[/TD]
[TD]p:+918056641187[/TD]
[TD]https://business.facebook.com/latest/26734856396184477?nav_ref=thread_view_by_psid[/TD]
[TD]complete[/TD]
[/TR]
[/TABLE]

Looking forward to your findings.

Thank you.

Hey @aniketnborhade,

Thank you for sharing the additional details.

Regarding the Odoo issue, we are not aware of any specific limitations with the Create Record action for these fields. Since the error originates from Odoo itself and the same values appear to work in the Update Record action, we will need a task history where the Create Record action is actively showing the error in order to investigate further.

For the Facebook Lead Ads issue, thank you for sharing the lead details. We have escalated the provided lead IDs and timestamps to our team for verification so they can check whether these leads were received from Meta's API and why they may not have triggered the workflow.

Please allow us some time to review this internally. Once we receive an update from our team, we will get back to you with our findings.