GENOSYN
Operations

Pipelines

Pipelines connect a trigger to predictable, repeatable steps. The same input follows the same connected path every time, and every Run records what happened.

Create a Pipeline

Open Pipelines from the section menu and choose Create pipeline. Name the outcome in plain language, add an optional purpose, then choose how the pipeline starts:

Manual
A Member starts it with Run now. Use this for one-off work, internal tools, and testing.
Schedule
Genosyn starts it automatically from a standard five-field cron schedule.
Webhook
Another system starts it by sending JSON to a private URL.
Email received
A genuinely new inbound email in a connected Gmail inbox starts it.
Task created
A new task in Projects + Todos starts it.

Choose Open builder. The trigger is already on the canvas; add what should happen next from the Step library.

Use the builder

  1. Select the trigger or an existing step. Choosing another item from the Step library places it after the selected step and connects it when there is one unambiguous path.
  2. Select a step on the canvas to open its settings. Complete the required fields marked with *.
  3. Use Next step in the Flow section to make or change a connection. For an If / else step, choose separate If true and If false destinations. You can also drag the dot on the right of one step to the left dot on another.
  4. Choose Arrange to lay connected steps out from left to right. This changes only their positions, not what runs.
  5. Follow the setup bar above the canvas. Run now stays unavailable until every required field and connection is ready.

Step library

Start the pipeline
Manual, Schedule, Webhook, Email received, and Task created triggers. A Pipeline needs at least one trigger.
Work in Genosyn
Send a channel message, add a task, create a Project, add a Base record, ask an AI employee, or write a journal note.
Transform or decide
Make an HTTP request, set named values, branch with If / else, or pause for up to 60 seconds.
Use a Connection
Choose a Connection and one of the actions its Integration exposes, then supply the action arguments as JSON.

Pass data between steps

Text and JSON fields can insert values with double-brace references. Data that started the Run lives under trigger.payload. For example, a webhook body like {"name":"Ada"} can be inserted with {{trigger.payload.name}}.

Each step also shows an Output reference in its settings. If a step's reference id is n_abc123, a later step can read one of its output fields with {{n_abc123.field}}. The Run's Step outputs section shows the exact object produced under each reference id.

  • A reference that fills the whole field preserves numbers, booleans, arrays, and objects. A reference inside a longer sentence becomes text.
  • JSON setup fields must contain an object. The builder checks syntax before enabling Run now.
  • Branch paths are labelled true and false on the canvas and in Flow settings.

Company event triggers

Event triggers start a Run when something changes inside the company. Add one from the Start the pipeline section of the Step library, then use its optional filters to decide which events should match.

Email received
Starts for genuinely new inbound messages in a connected Gmail inbox. Filter by sender, subject, or whether the message has attachments. Connecting an inbox does not replay historical mail into Pipelines.
Task created
Starts when a task is added by a Member, AI employee, recurrence, or another Pipeline. Filter by Project, priority, or words in the title.

Email data is available under trigger.payload.message, including from, subject, bodyText, hasAttachments, and receivedAt. Task data is available under trigger.payload.task, with its Project under trigger.payload.project. For example, use {{trigger.payload.task.title}} in a later message or task title.

Webhook Pipelines

Select a Webhook trigger to copy its private URL. Send a POST request with a JSON body; that body becomes trigger.payload for the Run. The Pipeline must be turned on for the URL to accept a Run.

Test and inspect Runs

Save the Pipeline and choose Run now. Genosyn starts a manual test with an empty payload, then opens Run history. Each Run shows:

  • whether it succeeded, failed, is still running, or was skipped;
  • what started it, when it started, and how long it took;
  • the step-by-step log and a plain error when a step failed;
  • the starting payload and the final output from every reached step.

Run now is always recorded as Started by a Member, even when the Pipeline normally starts from a schedule, webhook, or company event. Automatic Runs are labelled with the schedule, webhook, or event that started them.

Pipeline or Routine?

Use a Pipeline when the path should be deterministic: same input, same connected steps. Use a Routine when an AI employee should interpret a brief, choose tools, and decide how to complete the work. A Pipeline can still use AI for one specific decision by adding an Ask AI employee step.

PreviousTasksNextBases