Skip to main content
Question

How to Capture the Full JSON Payload Instead of Individual Dynamic Variables?

  • February 6, 2025
  • 1 reply
  • 9 views

Hi Zapier Community,

I’m facing an issue where I need to capture an entire JSON payload from an API response, but Zapier breaks it down into individual dynamic fields instead of giving me access to the raw JSON object.

My Current Zap Setup:

  1. Trigger: Webhook (Triggered by a prospect replying in Instantly).
  2. Delay: 3-minute delay to prevent immediate responses.
  3. GET Request: Retrieve a specific email ID (which isn’t available in the initial webhook payload).
  4. POST Request: Fetch lead information from Instantly’s API, which returns details such as:
    • payload website
    • payload email
    • payload firstName
    • payload lastName

The Problem:

  • Instead of getting the full payload as a single JSON object, Zapier forces me to pick each individual field (payload firstName, payload website, etc.).
  • This is a big issue because I will be duplicating this automation across multiple campaigns—each campaign has different payload structures, so manually selecting fields every time is not scalable.

What I Want to Achieve:

I need a way to capture and use the entire payload dynamically—meaning, instead of manually mapping individual fields, I should be able to reference {{payload}} as a whole in later steps.

Request for Help:

  • Is there a way to capture the entire payload object dynamically without breaking it down into individual fields?
  • Does Instantly’s API support returning raw JSON that I can reference later in Zapier?

Any help would be greatly appreciated! 🚀

 

Screenshots

Payload Received from Request
Instead of inputting all the information in ‘information’ - I want to add a step in between that aggregates anything that starts with ‘Items Payload’

 

Did this topic help you find an answer to your question?

1 reply

Forum|alt.badge.img+3

Hi, you can achieve this by employing a workaround that involves sending the parsed data to another Zap using a webhook. Configure your existing trigger as it is but in the URL field, enter the unique webhook URL generated by your second Zap (you’ll need to set this up).

In your second​ Zap, ​​​​​​use "Webhooks" with the "Catch Raw Hook" event. This will provide a unique webhook URL (which you have to paste in the first zap) to receive the raw JSON data and then add any subsequent actions you need to process the raw JSON payload.

When the first Zap runs, it will send the entire JSON payload to the second Zap's webhook, allowing you to handle the raw JSON data in its entirety.

Give it a shot and let me know!