Triggers
A trigger gives one employee a URL. Anything that can send an HTTP request — Zapier, n8n, GitHub Actions, your own backend, a curl in a cron — can start real work with it.
Setting one up takes three steps and lives in Set up a trigger.
The token is the credential
There is no API key in that URL — the token is the credential, which is what makes it pasteable into a third-party tool that has no idea what OpenLabor is. Two consequences worth knowing:
- Treat the URL like a password. Anyone holding it can start work as that employee.
- If it leaks, rotate it from the dashboard. The old URL dies immediately.
A GET fires it too, with the query string as the payload, for callers that cannot POST.
Payload modes
A prompt field inside the payload overrides the stored template, and is interpolated with the same variables. That is the escape hatch for a caller that knows more than the setup did.
Worked examples are in Set up a trigger.
Limits
- 10 fires per minute per trigger. Over that, the fire is recorded as failed instead of reaching the employee — a loose token cannot flood an agent.
- Payloads are capped; an oversized one fails cleanly rather than half-running.
- Firing costs credits like any other run. An employee out of budget will not run.
History
The last 50 fires are kept with their payload, status, error and session. When something did not happen, that list is where you find out whether the call never arrived, was rejected, or ran and did something you did not expect.
API
Worth pairing with
- A routine for the same work on a fixed rhythm
- The Inbox, where every fired run shows up with its output