Automations

Task 01 / Automations

Turn a rule on or off

Procedure / 2 steps

1. 01Callout 1. My Automations lists your rules. Use a rule's switch to turn it on or off.
2. 02A rule that is on and starts on Clip Detected runs once for each clip that clip detection finds in a project, best score first. One detection starts at most 30 runs. Clips found by a batch do not start rules.

Task 02 / Automations

Create a rule

Procedure / 4 steps

1. 01Callout 2. Press Automation Builder.
2. 02Press Create Automation Rule.
3. 03Name the rule, choose what starts it, press each action it should take, and press Create Rule.
4. 04On a rule, Run starts it by hand on the clip you choose, and Test shows what it would do without doing it.

Task 03 / Automations

Add a webhook endpoint

Procedure / 2 steps

1. 01In Automation Builder press Webhooks, then Create Webhook. Give it a name and the address to call. The events you pick are saved with it.
2. 02Press Test on a webhook to send it one request now and see the answer.

Task 04 / Automations

Receive an event when something happens

Procedure / 4 steps

1. 01Each event you picked is sent to the address when it happens: a project created, finished or failed, clips detected, an export finished, a batch started, finished or failed, a translation or a dub finished.
2. 02Press Show secret on the webhook to read its secret. Each request carries X-ClipForge-Signature: sha256= and the HMAC-SHA256 of its body, keyed with that secret, so the address can check that ClipForge sent it.
3. 03An event that does not get a 2xx answer is sent again up to three more times, a minute after the first try and then twice as long each time.
4. 04New secret replaces the secret. The old one stops verifying at once.

Task 05 / Automations

Connect an app in one press

Status

Connecting apps from here is not built. Zapier and Make work through a rule: add a Send to Zapier or Send to Make action and paste the hook address there.