Problems using Zapier zaps....

[blarney]

I have a few zaps that pull information between Shipstation (http://www.shipstation.com/) and a table in Caspio.  However, when the data is pulled in, a few columns are blank (storeid, item sku, and item name...all info that shipstation gets from shopify, although most shopify data is brought over, just not these fields). 

 

My work around is using a zap to a google sheet, then another zap to caspio. I'm not sure if the data type isn't compatible or what, but I can't imagine that they aren't in a text format....because the storeids are alpahnumeric and the item names wouldn't be anything but text, right?

 

The REAL issue with the work around is that the Shipstation to Caspio zap uses polling or maybe a webhook (I don't know how the zaps work tbh) to instantly update the caspio tables...which is what I'd prefer to do instead of waiting 5 minutes for the zap run (paid account).

 

Has anybody encountered an issue similar to this?  Any ideas of what could be happening and if there's something I could look at in my tables to try and fix this?

 

Thanks in advance!

[vishal]

Did you get this solved. I have the same usecase and dont want to implement this two-step process.

[Aether]

Hello! Caspio releases another new enhancement to the WebHooks feature, refer below: 

• Ability to send webhooks for tables with triggered actions 
• Ability to send webhooks based on changes in tables caused by triggered actions and application tasks
• REST API access to the count of created messages, calls, and received errors for webhooks from the past 30 days

Source: https://howto.caspio.com/release-notes/caspio-41-0/#:~:text=Enhancements to-,Caspio Webhooks,-(Beta)

[Aether]

Hello! Caspio releases another new enhancement to the WebHooks feature, refer below: 

Caspio Webhooks allows your applications to communicate with third-party systems in real-time when data changes occur.

Starting this release, you can configure webhooks to trigger based on how the data is updated, be it through DataPages, Datasheet, or REST API. Webhook payloads are enhanced by adding the ability to insert data source parameters or webhook-related parameters and to load a default payload.

Source: https://howto.caspio.com/release-notes/caspio-45-0/#:~:text=Enhancements to Caspio Webhooks

[Aether]

Hello! Caspio releases another new enhancement to the WebHooks feature, refer below: 

Latest enhancements available to non-HIPAA/Compliance accounts, webhooks can now be:

• Sent based on table events initiated by triggered actions and tasks.
• Configured for tables that have triggered actions enabled for the same event as the webhook.

Source: https://howto.caspio.com/release-notes/caspio-46-0/#:~:text=Enhancements to Caspio Webhooks

[FinTheHuman]

Hello! Caspio releases another new enhancement to the WebHooks feature, refer below: 

Caspio Webhooks allows your applications to communicate with third-party systems in real time when changes to data occur. 
In this release, we introduced the following updates:

• In non-HIPAA/Compliance accounts, webhooks logs now show the information sent and received.
• All accounts, including HIPAA/Compliance, now can:
  • Send webhooks based on table events initiated by triggered actions and tasks.
  • Configure webhooks for tables with triggered actions enabled for the same event as the webhook. 
• A single REST API call can be used to activate or deactivate all events for a selected webhook.

Source: https://howto.caspio.com/release-notes/caspio-47-0/#:~:text=Enhancements to Caspio Webhooks