Skip to main content
Best answer

How to remove the zapier default wrapper around trigger test's sample ?


wmarfil
Forum|alt.badge.img+1

Hello

 

I am making my custom app’s rest hook trigger using cli-integration. I make Zapier query my API to get a trigger test’s sample.

zapier default wrapper to my trigger test sample

How do I remove this ?I just want my API’s sample layer basically, to avoid huge labels for the user when mapping to action app such as:

 

How should I proceed ? 

Edit: i cant use static output field, this is a dynamic output field trigger based on the trigger input fields

 

Thank you

Best answer by Troy TessaloneBest answer by Troy Tessalone

@wmarfil 

It’s not an issue I would spend much time trying to address.

View original
Did this topic help you find an answer to your question?
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

4 replies

Troy Tessalone
Forum|alt.badge.img+14

Hi @wmarfil 

Good question.

You don’t have control over how Zapier parses and displays the data to the end user in the Zap Editor.

 

The label is shown as below because it shows the data hierarchy.

 

fulfillmentValue is an object.

ContactID is an object within.

f_EMail is a property within.

 


wmarfil
Forum|alt.badge.img+1
  • Author
  • Beginner
  • 10 replies
  • August 8, 2023

Hi Troy,

 

I am bit surprised that I cannot personalize this through my cli-integration performList function? 

These make the label pretty long.

All I can do is I guess flatten my object to make the label shorter.


Troy Tessalone
Forum|alt.badge.img+14
  • Zapier Expert
  • 30903 replies
  • Answer
  • August 8, 2023

@wmarfil 

It’s not an issue I would spend much time trying to address.


wmarfil
Forum|alt.badge.img+1
  • Author
  • Beginner
  • 10 replies
  • August 9, 2023

 

@Troy Tessalone 

Hi Troy,

Actually in my rest hook mechanism,

I find out that Zapier does not wrap the payload from my API, that occurs in the perform function hook, as opposed to performList hook. This breaks the mapping.

I made a separate forum post for this issue as it is blocking: