Set up a trigger

Let another system start the work: a form submission, a webhook, a GitHub Action, a curl in a cron.

Create it

1. Open the employee → Routines → add one (*when something happens*)

2. Name it, and write what the employee should do when it fires

3. Copy the URL and paste it into whatever will be calling it

The URL carries its own credential, so it pastes into a third-party tool that has never heard of OpenLabor. Treat it like a password, and rotate it from the dashboard if it leaks.

Turn the payload into an instruction

In template mode the payload fills placeholders in your prompt. Both {{var}} and {var} work:

In simple mode the employee gets the raw payload with a short note — the better choice when the payload shape varies and you would rather the employee read it than guess the fields.

Fire it once yourself

A GET fires it too, with the query string as the payload, for callers that cannot POST.

If nothing happened

The last 50 fires are kept with their payload, status, error and session. That list tells you which of the three it was: the call never arrived, it was rejected, or it ran and did something you did not expect.

Rate limits, payload caps and the full API are in Triggers.