That may help give you a clue as to whether those data points are initially available.
Otherwise, also check your Airtable Record Activity History, to see if changes are being made to that field values.
Thank you!!!! Great idea.
I checked out both histories.
First case: Regular running of the automation.
The automation creates a record in airtable from some information of a completed buy order in sendowl
This is what happens
This is a screenshoot of the data imported by zapier from the sendowl order
The “order custom checkout value” should appear on the airtable record.
Hw, this this the record created, as it can be seen the API doesnt import all the date.
Second case. Testing teh zap
I repeated the process creating a new fake order and testing the zap and the test work perfectly
I thing this is kind of a bug
David
This post has been edited by a moderator to remove personal information. Please remember that this is a public forum and to remove any sensitive information prior to posting.
Hi @Teatrero
Can you should a screenshot of how your have the Airtable Zap action step configured with the data points mapped from Sendowl?
Sure!!!
@Teatrero
I think the issue has to do with how the data is structured from Sendowl.
In the screenshots below, there are 2 fields for “name” and 2 fields for “value”.
Then when you have it mapped for the “value”, but I think what’s happening is when the Zap is ON and runs, it doesn’t know which “value” to map, and thus doesn’t send a value for the “Custom Fields” field to Airtable.
Yes!! what you mentioned is actually what i think is going on. But do you think there is any solution for that? All what i programmed on airtable depends on this custom field.
Should i open a ticket on sendowl?? zapier?? airtable????
Thanks for the help.
@Teatrero
FYI: Most Zap app integrations are created and maintained by the app developer on the Zapier Platform, rather than by Zapier, altho unsure who owns this Zap app integrations, so probably best to reach out to Sendowl.
