Hi @kpn95 

That usually means there is a naming convention difference for a data point, which is causing it to not map thru to Zap steps as expected.

Make sure you are using a Zap trigger example that has values for the data points your are dynamically mapping: https://zapier.com/help/create/basics/change-the-test-data-in-your-zap-trigger

Can you please provide screenshots of how your Zap step is currently configured?

@Troy Tessalone — thanks for the feedback. As I said the data is fine. Everything is mapped properly and works if I test it (in Zapier). I can refresh the trigger and pull in as much test data as I want; it’s always correct and always updates in the search step. I can even send live data to the record during testing. The Zap only fails during the live search step when the Zap is enabled.

It looks like this:

@kpn95 

Might be best to open a ticket with Zapier Support for them to troubleshoot with your further: https://zapier.com/app/get-help

I appreciate the input; unfortunately, Zapier Support has been unresponsive so far, but I will update the thread if I get more information.

@kpn95 

Best case to troubleshoot will be to look at the Zap Runs history details for triggered Zaps to see the DATA IN/OUT for each Zap step to see if you can determine where the issue is.

Is the desired data point actually being provided from the trigger step?

Is the desired data point named differently than what you have mapped?

Is the desired data point actually being provided from the trigger step?

Yes

Is the desired data point named differently than what you have mapped?

No

In essence, I can run the Zap manually with the “Retest & Continue” button, so I know the values are both correct and mapped properly, but as soon as the Zap is live, the search step fails to pull in the value from the placeholder (even though that value is in the JSON from the trigger). 

I believe that is what I referenced above. “Data Out” from the trigger step has the correct values but in the live Zap, the searchByValue returns a placeholder ( e.g., {{123426702__actor__id}} ) instead of an actual value.

I have also tried using a manual placeholder in the Zap step (e.g., {{actor__id}}), which will pull data from the JSON and push to Airtable successfully but only during the test step. It is only when the Zap runs that I encounter the error.

@kpn95 

I’ve seen where the sample data from the Zap trigger used to configure the Zap can be different then the live data that comes thru, which could include different data points or differently named data points.

Would need to see more screenshots of the live data returned for the trigger step in the Zap Runs in order to further evaluate and advise.

@kpn95

Otherwise, you may have to explore leveraging the Okta API/webhooks (https://developer.okta.com/docs/reference/)via the Webhooks app: https://zapier.com/apps/webhook/integrations

@Troy Tessalone I’m not sure if it helps, but here’s how it looks on my end:

@kpn95 

Is the “actor” data point nested under another data point?

FYI: Nested variable names are separated by 2 underscores __

@Troy Tessalone Per Okta documentation, it is not: https://developer.okta.com/docs/reference/api/system-log/

Again, I’m not sure if this helps, but here’s how the data looks in the Zap history for the manual placeholder ({actor__id}):

...and this is how it looks using the Zapier placeholder selected in set-up:

@kpn95 

FYI: The ID see at the start of the dynamic variable is the Step ID in the Zap.

You can see this in the browser url path by selecting a step in the Zap.

In that case, it seems like it should be pulling correctly, as the Step ID corresponds to the trigger event in the Zap. Any idea why that would break in the live version?

@kpn95 

I’ve honestly exhausted my troubleshooting efforts.

Has Zapier Support gotten back to you about your ticket?

@Troy Tessalone Thanks again for your effort.

They have not, unfortunately, but I am attempting to follow up with them andwill update the thread if I get a solution.

Resolution:

I was able to get in touch with the support team, which was extremely helpful.

First, this is a known issue with the data formatting in the webhooks. The developers are working on a technical solution, but in the meantime, support offered a couple of workarounds. The simplest was to update the value place holder to nest under “data” and “events” and, crucially, function as a string array. The format to pull actor__id was “{{123426702__data__eventst]actor__id}}.”

Of course this now doesn’t work in the testing step because of the difference in data formatting, but the live Zap is up and running.