Help center

    Start for free Sign in search

      Get Started Add Content Billing FAQs

      Automation action: Send web request 

      Thy Nguyen

      Updated on June 13th, 2023

      Table of Contents

      Webhooks are automated messages sent between apps—a type of notification that includes detailed information about new items in apps. 

      For actions that have not yet been supported by Gridly, you can use your favorite Automation tools like Zapier to connect Gridly with other apps.

      If you are not familiar with creating an Automation, please view the following article: Creating an Automation


      After creating the Automation, you need to configure the trigger and action. In this example we’ll create a draft in Gmail whenever the source language is updated (using Zapier by webhooks).

      Add “Record updated” trigger 

      1. Click Add Trigger, then select “Record updated” from the dropdown list.
      2. In the Watching columns section, select the Source language column (Source_EnUS). image1.gif

      Add “Send web request” action

      1. Click Add Step and select Send web request in the list of actions.
      2. Select the HTTP Method: Gridly offers POST, PUT, DELETE methods.
      • Use the POST or PUT methods if you’re sending files.
      • Use DELETE if you want to delete a resource from the server.

      In this example we’ll select the POST method to send data from Gridly to Zapier. 


      Get webhook URL from Zapier

      1. Open Zapier, create a Zap and add the Webhooks by Zapier action, then select Catch hook in the Event dropdown menu and click Continue. You can follow this help article. 
      1. In the URL field, enter the URL where your app’s API is able to receive requests. In this example, we’ll copy the Webhook URL from Zapier and paste it to this field. image8.pngimage5.png
      2. (Optional) You can send specific Headers by filling the fields in the Headers section.
      3. (Optional) Select input value for action: Gridly supports JSON as the serialization format, so remember to input your payload in the correct format. 
      4. (Optional) Output fields: Output variables let us pass data from the Send web request action to any remaining actions in the Automation run. 
      5. (Optional) Postbacks: Map the output fields from Lambda function to the columns in Gridly, this helps Gridly update the returned values from Lambda functions to correct columns.



      If your webhook endpoint (URL) is behind a firewall/private network, you’ll need to whitelist our IP address:


      Test Automation

      1. Switch the toggle on to turn on the Automation
      2. Click Test Automation. If your Automation is not turned on, Gridly will require that you turn on the Automation in the resulting pop-up message. Click on the toggle to turn on and select Test again.
      3. Open Zapier again and click the Test trigger. Test the webhook step in Zapier, and you'll see data from the webhook listed in Zapier.


      Webhook request timeout

      Webhook requests sent by Gridly have a maximum timeout of 75 seconds. If a webhook request takes longer than the timeout to complete, the automation rule will be shown as “Failed” in the Run history.


      Run Automation

      Now you can use the data and send it to another app action. In this example, we’ll create a draft in Gmail using this data in Zapier. You can follow the instructions in this article. Here’s the customized payload in Zapier:


      And you’ll see the mail in the Draft: 


       To view all related articles to Automations, click here.

      Was this article helpful?

      0 out of 0 found this helpful

      Still need some help?

      Contact Support