CONNECTED TOOLS

Keep your tools.
Connect what they can do.

Find an app, connect an account, and see the actions available to you. Bring supported tools into the workflows and responsibilities already running in Ralti.

THE WORK, IN CONTEXT

Give the next step the right tools.

Use available connection tools inside the workflow.

Illustrative example
↗A published flow

When it is time to act

⌘Connected tool

Choose the action
Map the inputs
Review the result

▦Shared records

The next step has context

CLEAR FROM CONNECTION TO ACTION

Find it. Connect it. Put it to work.

A consistent setup, visible connection status, and tools you can inspect before using them.

Authorized tools onlyAvailability varies during beta
Fictional example to explain the experience. Product screens and available actions depend on your setup.
01

Find the right connection

Browse a searchable library with recognizable app logos and categories. Navigation and filters stay in place as you explore results. Open an app to see its connection route and the tools it can expose.

  • Search, category filters, and account management
  • Reuse an existing verified account or connect a new one
  • A consistent Connection → Available tools → Ready journey
02

See the action before you use it

Supported tools have their own input forms, version, and permissions. Configure the required details, inspect available options, and choose which output fields later workflow steps may use. Connecting an account alone does not run an action.

  • Supported provider actions and approved API-request tools
  • Use in a Flow opens an editable, unsaved workflow
  • Credentials stay out of ordinary action inputs
03

Put connected tools to work

Add Use an integration to an existing Flow. Map earlier results into the tool’s inputs, review the intended action, and publish the process when it is ready. App journeys and agent proposals use the same connected-tool foundation.

  • Review by default; eligible flows can explicitly allow automatic execution after publishing
  • Agent delegation names the exact account and tool
  • An uncertain external result is held for reconciliation rather than blindly repeated
04

Start with what is supported today

Integrations are in a controlled early-access rollout. Account connection, action execution, and bringing external data into a sheet are distinct capabilities. The PostgreSQL source route offers reviewed discovery, preview, mapping, and import; other apps offer source setup only when their adapter supports it.

  • A catalog listing is not a guarantee of sync, write-back, or every provider action
  • Availability depends on account eligibility, provider authorization, and supported tool inputs
  • Check connection status, reconnect, or remove a workspace’s account link

Understand connection setup and availability
Build a connected workflow

GOOD QUESTIONS

A little more clarity.

Does connecting an account automatically sync its data?

No. Connection verifies an account. Sync or import needs its own supported source setup; an action needs explicit configuration and execution.

Are all catalog apps ready for every user?

No. The library includes upstream catalog entries, while Ralti rollout eligibility and support are checked separately. Some tools need additional authentication or input types that are not supported.

Does removing a connection delete my data elsewhere?

Remove from Ralti removes the saved link in the current workspace. It does not revoke authorization at the provider or delete native records. Dependent sources must be handled first.

YOUR NEXT CHAPTER

Big plans start here.

Find your fit with a Free Forever workspace at launch.

Get early access ↗