Restricted filter options for webhook automation

🙏 Ask the Community
,
1

Hi Tape Community,

this is my first question here, and I’m excited to get some bright minds to look at my issue.

Current state:
We have two automations that trigger the creation of a customer profile, both based on a webhook connection to our website.

Problem:
The automations are triggered either by filling out contact information or by using a calculation service on our site. Often, users do both, which leads to duplicate customer profiles.

Goal:
I want to extend the filters in the automation so that, if the email address already exists in our customer database, the creation of a new profile is prevented.

My struggle:

P 0
P 01920×753 87.4 KB

Unfortunately, I don’t have much flexibility when choosing fields for filters and conditions.

In the screenshot below, you can see that the field “Webhook payload / ichBin” was selected in a previous step:

Because of this, my available options are now limited to either the same field or generic webhook data.
I don’t have the option to manually reference something like “Webhook payload / email”, even though this field does exist.
Additionally, these are the only options available for the reference field:

What I would like to do:
I want to reference the field “Webhook payload / email” and check it using “does not include” against a field that contains all existing email addresses (as a list/vector).

Is this possible? Or am I approaching this the wrong way?

Thanks a lot for your help in advance!

Best regards,
Leonard

1 Like
2

@Leonard_Young

First off welcome, now really quickly and I will try and look in more detail later however:
If you give the Automation a Payload then the options will appear - either fire off a test to it or if you go to the manual run top right you can paste in a payload, via the ‘Custom Payload’ option:

View Screenshot
View Screenshot1200×550 78 KB

run the Automation and the extracted fields will then be available for you.

4 Likes
3

Hello Jason,

thx for the quick reply, it is greatly appreciated.
I will try and see if it helps.

Best regards
Leonard

2 Likes
4

I was today years old when I learned you can copy/paste a custom payload to get fields.

It’s always been such a PIA to send live data while building everything out.

Not sure how I missed that before :rofl:

1 Like
5

Yea it is such a great little feature enabling you to control the payload during testing, that along with switching from the payload ‘variables’ view to the JSON payload view:

View Screenshot
View Screenshot1200×488 127 KB

Are such useful things.

1 Like
6

I made a little video about this, to try and be clearer:

5 Likes
7

I get this system feedback, do I need more rights do edit?
Or do i have to change a mode?
Thanks in adcance! :smiley:

grafik
grafik1474×406 30 KB

8

Look at 30s in the video @Jason shared in his last comment.

You need to manually run with a custom Payload. Then you can call the @tokens in your item

2 Likes