Webhook destination

Adding a webhook destination to Powersave allows you to send data to any URL. Effectively this means you can send data to an Airtable automation with the incoming webhook trigger but you can also send data to workflow platforms such as Zapier, Make. Technical users can also send data to their own custom web servers.

Usage with Airtable automations

If you decide to send data to Airtable webhook, it gives you more flexibility. You can adjust the data before you create a record out of them. You can create multiple records right away - perhaps two interlinked records.

Airtable automations also allow sending Slack messages, create Google calendar events and other custom actions.

Usage with workflow platforms such as Zapier or Make

All well known automation platforms support "incoming webhook" triggers. Powersav can effectively send data to such a trigger and afterwards, the possibilities are virtually limitless.

Zapier and Make and other integrate with thousands of different platforms so this is the way to go, if you want to send data to a custom place, besides Airtable.

URL

Here you need to paste the URL of the webhook. As you set up a new workflow in Airtable and other platforms - that special URL will be given to you. Sending data there will effectively trigger the workflow / automation.

Request method

Most platforms require this method to be POST. But for advanced cases you might set up different methods here like PUT or PATCH perhaps if you're sending data to a specific platform directly.

Headers

In most cases no headers are required to be set. But if you're sending data to specific API, you might take use of setting up an authorization header.

Fields

Powersave is opinionated in the way it uses Fields with webhooks. As you configure and fill your fields and hit Save, Powersave will construct a payload out of it and send it to the webhook URL. For Create one it might look like this:

{
  "Product Name": "Powersave",
  "Tags": ["Chrome Extension", "Automation", "Airtable", "Webhooks"]
}

It depends on the fields.

In case you're using the Create many tab, the individual "records" are scoped under data

{
  "data": [{
    "Product Name": "Powersave",
     "Tags": ["Chrome Extension", "Automation", "Airtable", "Webhooks"]
  }, {
     "Product Name": "Slack",
     "Tags": ["Messaging", "Teams", "Management"]
  }]
}