Typed connectors with credentials kept out of sight, SOAP and JDBC for the systems that predate REST, message brokers in, webhooks out, connectors that write themselves — and Atoms, a hybrid runtime that executes flows on your own premises and returns only the result.
Install a connector from the Marketplace, store credentials in an api Connection, and call its operations from the connector step with typed inputs and mapped outputs. The step-config UI walks you from connector to operation to inputs to connection — no URLs, no headers, no secrets in variables.
audit_appasync_job_drain creates, polls to completion on durable intervals, and drains paged resultsEnterprise integration is mostly not JSON over HTTPS. FlowClick speaks to the rest through typed connections that keep credentials out of flows and put every call on the same audit trail.
filesystem step: read, write, list, verify, and apply WORM retentionDescribe the vendor API to a governed agent and it drafts a connector descriptor and fixtures as a proposal. The platform re-runs the fixtures itself, records a verdict, and waits for a person to approve. Only then does the connector go live — for your account, or published to the Marketplace.
An Atom is a lightweight FlowClick runtime installed behind your firewall and paired to an application. Flows you assign to it execute entirely on your network — against your databases, your file shares, your internal APIs — and only the result comes back.
atom stepA subflow call that runs on a named Atom. Inputs go in, outputs come out; the flow definition, version, and audit stay in the cloud where you manage everything else.
exec stepRun local command-line tooling on an Atom — build tools, git, CLI agents — through a named exec connection, with output captured into the flow.
Model training can be dispatched to an Atom so sensitive data never leaves the premises; the trained artefact registers centrally like any other version.
Atoms enrol outbound with a credential you can reissue, keep a health view in the account, and are reached over an authenticated channel — no inbound ports on your network.
Decide per flow what runs where, from the UI or over MCP. Move a flow back to the cloud with one call when the constraint goes away.
An Atom run is traced, audited, and effect-budgeted like any other. QA sessions capture its side effects instead of firing them.
Consume Kafka, Amazon SQS, Google Pub/Sub, AMQP, polled endpoints, and reliable webhooks — one flow run per message, at least once, deduplicated, optionally ordered. Publish platform events to your systems as signed HTTP callbacks with retry policies.
SOAP, an on-prem database, a vendor with no connector — we'll show you the path for each, including one that builds itself.