Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Best answer

How do I get webhook params that don't exist on an example?

A

I have this URL:

https://account.tallyfy.com/register?utm_source=tallyfy.com&utm_medium=organic&utm_campaign=definition-client-onboarding&utm_content=get-started&gclid=ABC123&gclsrc=ABC123&fbclid=ABC123

… which essentially contains a bunch of GET params. 

Everything in the GET params will be passed to a Zapier endpoint which listens to a webhook and then shows them up like this (that works).
 

 

The problem is simple, I know that OTHER params e.g. &something=somethingelse can and WILL exist in future and I need to use them in my zap, even though the example does not have them

 

This is a common problem - webhooks can have a variable set of fields/keys - some webhook examples have them, and some do not.

How do I use/refer to keys/entries that don’t exist yet in the example trigger?

Best answer by Troy Tessalone

Hi @amitarelli 

Try testing with an example that has ALL of the possible query string parameters and/or values you’ll need to configure your Zap.

 

A more advanced way of deriving and mapping data points is to copy/paste a mapped query string data point from the trigger step into a browser which will return something like this

{{12345678990__querystring__test}}

The numbers at the start indicate the Zap Step ID.

The “querystring” bookended by double underscores indicates the data point is a query string paramater.

The “test” is the name of the query string parameter.

So if you know the names of the query string parameters that you’re trying to map you can artificially create those and copy/paste them into the desired field to be mapped.

 

Example below shows 2 mapped query string paramaters “Test” and “Tester” where currently only the “Test” query string parameter is present in the trigger data, but if “Tester” were to be included in the query string data it would map thru as expected.

NOTE: Always be sure to TEST!

 

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

4 replies

Troy Tessalone
Forum|alt.badge.img+14
  • Troy TessaloneZapier Expert
  • Zapier Expert
  • 31147 replies
  • Answer
  • March 18, 2021

Hi @amitarelli 

Try testing with an example that has ALL of the possible query string parameters and/or values you’ll need to configure your Zap.

 

A more advanced way of deriving and mapping data points is to copy/paste a mapped query string data point from the trigger step into a browser which will return something like this

{{12345678990__querystring__test}}

The numbers at the start indicate the Zap Step ID.

The “querystring” bookended by double underscores indicates the data point is a query string paramater.

The “test” is the name of the query string parameter.

So if you know the names of the query string parameters that you’re trying to map you can artificially create those and copy/paste them into the desired field to be mapped.

 

Example below shows 2 mapped query string paramaters “Test” and “Tester” where currently only the “Test” query string parameter is present in the trigger data, but if “Tester” were to be included in the query string data it would map thru as expected.

NOTE: Always be sure to TEST!

 

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
A
  • amitarelliBeginner
  • Author
  • Beginner
  • 2 replies
  • March 18, 2021

@Troy Tessalone many thanks! I will use the query string method (form my own definitions) as I am unable to “fake” the webhook at this time (it’s in production).

For the first part - the zap step ID - where do I get that from?

Also - I wanted to confirm on this example {{12345678990__querystring__test}} 

  1. Are all separators double underscores?
  2. Is the second segment querystring always fixed, no matter what?
A
  • amitarelliBeginner
  • Author
  • Beginner
  • 2 replies
  • March 18, 2021

@Troy Tessalone also note my trigger is a webhook, not a URL. Is that what you understood? I am receiving a webhook with a varying set of keys like this.

 

Webhook A:

{ KEYA: VALUEA, KEYB: VALUEB }

Webhook B:

{ KEYA: VALUEA, KEYC: VALUEC }

 

Notice how KEYC is in webhook B, but not in A.

Troy Tessalone
Forum|alt.badge.img+14

Hi @amitarelli 

Depends on how the webhook is being sent: GET vs POST

If via GET method, then the guidance above will work.
You can get the Zap Step ID by mapping another trigger data point in a Zap action step, then copying/pasting that into a browser to reveal the double encoded variable format {{variable}}.

If POST, then the variable format for those parameters will not include the __querystring__

Best advice: When in doubt, test it out.

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor

Reply


Terms & Conditions