Zapier Integration and Field Values of Custom Fields not pulling through

If Deal Values are showing up as blank, there are a few common causes to check:

Here’s what you should look into:

1. Webhook Configuration
   Double-check that you’re using the correct webhook trigger and that it’s firing on the right event (e.g., deal_add, deal_update). Not all events automatically include full Deal Value data.
2. Timing of the Webhook
   Sometimes, if the webhook fires immediately after deal creation, the values (especially custom fields or calculated totals) may not have been fully saved yet. If possible, try delaying the webhook trigger or sending it on a slightly later event like a status update.
3. Custom Deal Fields vs. Deal Value
   Custom fields may be included directly in the payload, but the actual “Value” of the deal (as in the monetary amount) is usually in the value field. Make sure you’re referencing the right part of the JSON.
4. Zapier Parsing
   Zapier sometimes shows blank values if the sample data doesn’t include populated fields. Try capturing a new sample webhook with a fully populated deal to see if the data comes through.

What you can try next:

• Re-send a test webhook using a Deal that has a confirmed Deal Value.
• In Zapier, check the raw webhook data (under Zap history) to see if the value is actually missing from the payload or just not mapped properly.
• Review the Developer Webhook documentation for Deals to ensure your setup includes the correct parameters.

Thank you so much for your help. Since I was looking for a specific field update for the ZAP to continue I needed to change the webhook from “Deal Added” to Deal Updated". Now I am sitting with the problem that the ZAP is running multiple times. My assumption is because multiple fields are updated (even though only one “Save”) it is sending every field change update to Zapier. I changed it to a different event to delay the timing, very limited options so I chose a Task Created but now I would need to gather that task Info to send back to close the task as well which is creating more and more complexity. Is there no way Deal updates can be send via Webhook in an automation? I am not if it is possible for Zapier to compare records to determine to only use once? Any further guidance would be appreiated

Hey!

The behavior you’re seeing (multiple triggers from a single “Save”) happens because AC’s webhook system sends an individual webhook for each field that changes rather than bundling all changes into a single webhook. This design can be helpful for some use cases but can create exactly the situation you’re experiencing.

Here are a few approaches that might help:

1. Use Zapier’s Filter step: After your webhook trigger, add a Filter step to only continue if a specific field has changed to a specific value. For example, “Only continue if Deal.Status equals ‘Won’” - this would prevent the duplicate runs for other field changes.
2. Implement a “cooldown” using Zapier’s Delay: Add a 1-2 minute delay step after your webhook trigger. Then use Zapier’s “Dedupe” feature to only process the most recent entry for each Deal ID within that timeframe.
3. Use a “flag field” approach: Create a dedicated custom checkbox field on your Deal like “Ready for Zapier.” In your ActiveCampaign automation, only check this box as the final step after all other deal updates are complete. Then in Zapier, filter to only process webhooks where this field equals “Yes” and use another automation step to uncheck it afterward.
4. Switch to the API polling trigger: Instead of webhooks, you could use Zapier’s “New Updated Deal in ActiveCampaign” trigger which uses polling and tends to batch changes better.

For your Task approach - you’re right that it adds unnecessary complexity. I’d recommend trying the filtering method first as it’s usually the simplest solution.