Skip to main content

Configurations

FluidGrids is a managed service, so there is no server configuration to maintain. What you do configure is how your clients reach FluidGrids, and how your workflows behave when they run.

Connecting a client

ClientSettingNotes
CLIFLUIDGRIDS_API_URLOr pass -u/--url, or run fluidgrids config set url <endpoint>
Node SDKFLUIDGRIDS_ENDPOINTOr pass endpoint when constructing the client
Python SDKFLUIDGRIDS_ENDPOINTOr pass endpoint= when constructing the client
Browser / VS Code extensionsBURDENOFF_ENVRead only by the extensions, not by the CLI or SDKs
MCP serverFLUIDGRIDS_GRAPHQL_URL, FLUIDGRIDS_API_URLPlus FLUIDGRIDS_ACCESS_TOKEN

All clients default to production. See the FAQ for the endpoint values.

Authentication

SettingDescription
FLUIDGRIDS_API_KEYWorkspace-scoped API key, created under Developer Portal › API Keys in the app

API keys are scoped to a single workspace and are audit-logged on every use. Rotate them from the same screen that issues them; revocation takes effect immediately.

Keep keys out of source control. Read them from your own secret store or your CI provider's encrypted variables.

Workflow execution settings

These are configured in the product, not by environment variable. Workspace-wide defaults live on the workflow module's Settings screen (/workflows/settings); per-node behaviour is set in the node's Settings tab in the builder:

SettingWhereDescription
Default TimeoutSettings › ExecutionHow long a run may take before it is stopped
Max Retries / Retry DelaySettings › ExecutionAutomatic retries on failure and the wait between them
Concurrent Execution LimitSettings › ExecutionHow many runs may execute at once in the workspace
Per-node retry and error handlingNode › SettingsWhether a failed node is retried, and whether the run continues on error

Plan limits cap the maximum values; the workspace's own settings apply below those caps. See Settings and Plans and Quotas.

Next steps