Allows you to provide multiple HTTP endpoints, that receive a more complete JSON from the run, and allow you to hit those endpoints using a proxy, and enable you to do conditional webhook calls with some lines of Javascript code and you can link/chain one actor to another

Existing actor IDs that will be modified to receive the webhook configuration.

Actor IDs

Any custom data that you want to add to this specific configuration

Custom data

Optional emails that should receive the digests. You need to specify this or the HTTP Endpoints parameter

Emails

HTTP(s) endpoints that will receive the run information through a JSON POST. Configure your data below on "Transform endpoint data" field

HTTP Endpoints

If you need the data to be sent using PUT instead of POST, change this here

HTTP Method

Optional proxy setting. Use this if you need to use an specific proxy to connect to the remote endpoint, like a StaticUS group

Proxy

Run statuses

Existing task IDs that will be modified to receive the webhook configuration.

Task IDs

Optional token to install in another account

Account token

Allows you to transform the output data to fit an specific format, like MS Teams or another Apify actor input, like Slack Notification. Must return an object or an array

Transform endpoint data

Allows to filter when endpoints and emails will be called depending on the state of the run

Trigger condition

Run digest email

run-webhook-digest

Power Webhook Integration

Power Webhook Integration · Apify

API · Power Webhook Integration · Apify

Input · Power Webhook Integration · Apify

Related actors · Power Webhook Integration · Apify

Allows you to provide multiple HTTP endpoints, that receive a more complete JSON from the run, and allow you to hit those endpoints using a proxy, and enable you to do conditional webhook calls wit...

Where next?