How to format query strings in Zapier Webhook GET request to Caspio API

[MVPofInnovation]

I feel like this should be simple, but I'm stuck. I'm trying to get querystrings to work in a zapier Webhook GET step for a zap to update Caspio via API.

Here is the URL: https://xxxxxxx.caspio.com/rest/v2/tables/tbl_contacts/records?q.where=crm_contact_id=338020465

But, in Zapier Builder I have to break up the URL into the base URL with separate queries.

It's got one box for the param, and one box for the data. I've tried a bunch of different combinations and still don't get the expected result -- it just keeps returning all records.

What goes in the Param box and what goes in the data box? Do I need to add a "?" to the end of the URL?

 

[CoopperBackpack]

Hello @dhudiburg,

I am not aware of a syntax that should be used in Zapier. 

But in Postman it looks similar


Have you tried to test it with the syntax as on the screenshot? 

[Aether]

Hello Everyone, have you already checked this new feature of Caspio called "Webhooks"?
This is kind of similar to Zapier which automates integrations between different applications.
For further details check it here. https://howto.caspio.com/webhooks/webhooks-overview/

[Aether]

Hello Everyone, have you already checked this new feature of Caspio called "Webhooks"?
This is kind of similar to Zapier which automates integrations between different applications.
For further details check it here. https://howto.caspio.com/webhooks/webhooks-overview/

[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

[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 data changes occur.

The system now supports configuring multiple webhook events of the same type per table — whether for inserts, updates, or deletions. This enhancement removes the previous limitation where only one webhook event per action type could be set up for any table.

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