Skip to main content

Standalone activities

Sometimes you only need one reliable call: send this message, write this row, call this API, with retries and a record of what happened. A standalone activity runs one node operation as a durable run, without a workflow of your own.

Start one​

From the CLI:

fluidgrids activity start store/slack sendMessage \
--args '{"channelId":"C0OPS","text":"Order 7 shipped"}' --wait

Run fluidgrids activity start --help for the connection, retry and timeout options.

From the GraphQL API:

mutation {
startActivity(input: {
nodeType: "store/slack"
operation: "sendMessage"
args: { channelId: "C0OPS", text: "Order 7 shipped" }
connection: "<connection id>"
retry: { initialInterval: "2s", backoffCoefficient: 2, maximumAttempts: 5 }
startToCloseTimeout: "30s"
summary: "Tell ops that order 7 shipped"
idempotencyKey: "order-7-shipped"
}) {
existing
run { id status }
}
}

From Node.js with @fluidgrids/sdk: activities.start({...}), then runs.result(runId) to wait for the outcome.

InputMeaning
nodeType, nodeVersion, operationThe node operation to run
argsIts arguments, as literal values
connectionThe id of the connection the operation uses. You can only use a connection you are allowed to use; any other is refused before the run starts
retryinitialInterval, backoffCoefficient, maximumInterval, maximumAttempts, nonRetryableErrorTypes
startToCloseTimeout, scheduleToCloseTimeout, heartbeatTimeoutTimeouts, as in Activities
summaryA label for the run
idempotencyKeyStarting again with the same key returns the existing run (existing: true) instead of a new one

What you get​

The call returns a run straight away. It is an ordinary durable run: it appears under Executions, and its History tab shows the activity being scheduled, started and completed, with every retry. Cancel or terminate it like any other run.

Only node types that may run as activities can be started this way: store and registry nodes, HTTP Request, Data Table, Set and Code. Anything else, for example IF, is refused before a run is created.

Permissions and quotas​

Starting a standalone activity needs permission to execute workflow runs. The run uses the connection with your permissions, as the person who started it. Each one counts as one run toward your plan's monthly runs, and its activity attempts count like node executions.

Next steps​