Guides

Connections

Named, reusable records for the outside services your server talks to — enrolled once, granted per pack.

A connection is a named record for an outbound endpoint your server talks to: an API such as a CRM, an MCP tool server, or a notification target. Packs request operations against a connection by name; the credential itself is enrolled once and reused, never copied into recipes.

#Enroll a connection

Open Settings → Connections and choose a provider, or let a pack that needs one walk you through enrollment during its install. Each connection is keyed by kind and name — acme-hubspot and personal-hubspot are independent connections with independent grants.

#CRM vendors bring their own app

HubSpot and Salesforce enroll through an app you create in your own vendor account — a developer app for HubSpot, a Connected App for Salesforce, with a sandbox toggle. Recued's cloud provides only a static OAuth callback page; tokens are exchanged and stored by your server. There is no central broker holding everyone's tokens.

After enrollment, the provider's actual permissions are verified — granted scopes for HubSpot, object-visibility probes for Salesforce — and anything missing surfaces as a warning on the affected capability instead of a silent gap.

#Where credentials live

Credential material stays on your server and is used only at call time by the connection executor. Recipes can read a connection's non-secret fields, but auth material never enters recipe data or step outputs.

#What connections power

  • CRM collections in the warehouse, reconciled from the vendor and accelerated by webhooks or streaming.
  • Outbound notification posts, such as email fan-out through a named target.
  • MCP tool servers your recipes can call.

#Sending mail

A mail account advertises whether it can send. Recipes check that capability before attempting a send, the server re-checks at the moment of sending, and a guard refuses self-addressed loops. Outbound mail goes from your server to your provider — it is never routed through Recued's cloud.

#Lifecycle

Recipes reference a connection by name, so deleting one stops dependent capabilities from resolving until a connection with that name is enrolled again. Grants attach to installed packs; you can revise access without re-enrolling the credential.

Recued is local first; your server remains the authority.

Recued Docs

Search documentation

Start typing to search the documentation.