> For the complete documentation index, see llms.txt.
Skip to main content

Check out Port for yourself ➜ 

Workflow trigger

The workflow trigger lets other workflows run your workflow. A parent workflow calls it with an execute workflow node, and the input it passes is available as the trigger's output.

Use it to build a dedicated sub-workflow, or to let an existing workflow also be called by others.

Beta

The workflow trigger and the execute workflow node are in beta and may change.

Add the trigger in the builder​

You can add a workflow trigger in two places:

  • New workflow: in the trigger picker, under Another workflow, select When called by another workflow.
  • Existing workflow: open the Add node dialog, go to Add another trigger, and under Another workflow select When called by another workflow.

A workflow trigger is always added as a standalone trigger with no incoming connection, even when you add it from a node's + button. A newly added trigger is published.

Configure the trigger​

Select the trigger to open its form. You can edit the title, icon, and description, which help you recognize the trigger on the canvas and in the trigger list of other workflows. You can also set the Published toggle.

When Published is off, other workflows cannot execute this workflow through this trigger. Use it to turn off an entry point without deleting it.

Deleting a workflow trigger

Deleting a workflow trigger, or a workflow that has one, breaks any other workflow that executes this workflow through that trigger. Port warns you before you confirm the deletion.

Configuration​

A workflow trigger node has the following config:

{
"identifier": "called-by-workflow",
"title": "When called by another workflow",
"config": {
"type": "WORKFLOW_TRIGGER",
"published": true
}
}

The workflow trigger has no input schema. The calling workflow decides what to pass in the input field of its execute workflow node, and the child reads it from the trigger's output, for example .outputs.trigger.service.

Published​

The published field controls whether other workflows can execute this workflow through the trigger. When set to false, an execute workflow node that targets this trigger fails until the trigger is published again.

PropertyTypeDefaultDescription
publishedbooleantrueWhen `true`, other workflows can execute this workflow through the trigger. When `false`, the trigger is disabled.

This is useful for temporarily disabling a workflow without deleting it, or for creating workflows that are not yet ready for production use.

Next steps​