Actions

Actions run work on a recurring cron schedule or once at a set time. When an Action is triggered, it creates an Invocation that calls a path on one of your Services over HTTPS.

Operating model

An Action belongs to a Project and targets a path on one Service. Its schedule is either a cron expression with a named time zone or a single ISO 8601 instant. Each scheduled attempt creates an Invocation with its own state, request, response, logs, and retry history.

You can create Actions from the console, CLI, or API. Pausing an Action prevents new scheduled invocations without deleting its history. You can invoke it manually while testing the handler.

Responsibility boundary

Forte operates scheduling, trusted request delivery, invocation state, and configured retries. You own retry-safe handler behavior, execution duration, authorization beyond the trusted Forte request, downstream side effects, and recovery after a partial success.

Actions are in Open Beta: all accounts can use them, while limits and interfaces may change before GA. See feature maturity.