Syncing custom fields from Deal to Organization in Pipedrive

Hi ​@Patrick Flamant 

For us to have more context, post these screenshots:

• how your Zap steps are outlined
• how your Zap steps are configured in the CONFIGURE tab while in EDIT mode with the field mappings visible
• the encountered error

Hey ​@Patrick Flamant,

The error basically means that the fields was empty during the run. Please check if you are mapping it correctly.

For live zaps, see the Zap history here- https://zapier.com/app/history to spot any issues there. Make sure to pass the Organization Id and not the name. Your workflow will look something like this-

• Deal Updated or Deal Matching Filter trigger
• Filter to check if custom fields are empty
• Find Organization action
• Update Organization action

Hope it helps!

PS: If you need more active help, I’m happy to connect through my Zapier Solution Partner page if you’d like to reach out here- https://zapier.com/partnerdirectory/automation-jinn

This usually means Zapier is reaching the Update Organization step, but Pipedrive is not actually receiving any new value to write.

So even if the fields are mapped, the update can fail if:

• the deal field is empty

• the field value is not coming through in the test

• the mapped field/key is wrong

• the value format doesn’t match what the organization field expects

For dropdown fields, that last one is a common problem.

I’d check these first:

• make sure the deal custom fields actually contain values in your test record

• use the field picker in Zapier if possible, instead of only pasting API keys manually

• confirm the Organization step is getting the value from the Deal step

• for single-select / multi-select fields, make sure the value format matches what Pipedrive expects

So the error usually doesn’t mean the zap logic is wrong it just means the update step is receiving blank or unusable field data.

Hi ​@Patrick Flamant 

Here's the Zapier doc that might help: https://help.zapier.com/hc/en-us/articles/33088851998349-Pipedrive-error-Nothing-could-be-found-for-the-search

The "At least one field must be provided" error usually happens when Pipedrive expects option IDs (numbers) but receives option labels (text) instead. This is common with dropdown fields.

If you're still running into issues, drop a screenshot of your Zap setup (especially the mapping in your update step) and I'll take a look!

And if you'd rather just get it sorted quickly, I offer a free 20-min Zapier troubleshooting call. Book it under Resources on my Zapier Directory profile: https://zapier.com/partnerdirectory/automatemybiz

This usually means the Update Organization step is reaching Pipedrive, but Zapier isn’t actually sending any usable organization field value in that step. Zapier’s Pipedrive action only does a partial update, so if all the mapped org fields are empty / unmapped, Pipedrive returns exactly that kind of error.

So I’d check 3 things first:

• make sure the Organization ID in the update step is the correct one

• make sure at least one organization custom field is really mapped with a value coming from the Deal

• retest with a fresh deal where those fields definitely contain data

My guess is the API keys themselves are probably fine — the issue is more likely that the update step is not receiving any actual new value to send.