Four ways to start
- 01Manual: an operator launches the run and answers its launch questions.
- 02Schedule: the run starts at a set time, every day or on the cadence you choose, with saved inputs.
- 03Event: a matching email reaches the workspace inbox, and the inputs are extracted from the message and its attachments.
- 04API: another system sends an authenticated request with the inputs.
Email events
Much back-office work still arrives by email: a broker sends an application, a vendor sends an invoice, a client asks for a statement. With an event trigger, the request lands in the workspace inbox, Ramain extracts the fields the workflow needs from the body and attachments, and starts the run.
Receiving the message, extracting its fields and launching the run are recorded as separate events, so when a request did not start a run you can see which step stopped it.
API launches
A published workflow can be called from your own systems. Each call uses a key scoped to what it may do, such as starting runs or reading results, and any key can be revoked. An external system can start the work without being given access to the portal itself. The developer docs cover the request and the callback when a run finishes.
One workflow, many starts
You build and test a workflow once. Adding a schedule or an email trigger does not change what it does in the browser, only how its inputs arrive. Disabling the workflow pauses new launches from every source at once.