Connections

Before you connect

You need an owner or administrator role in the workspace. Open Connections and check the selected business. Connections belong to that business, so an account configured elsewhere will not appear as an available account here.

Use the connection catalog to review setup requirements and supported operations. A service listed in the catalog is available to configure; it does not mean your account is already connected.

Add and verify an account

1. Choose the service.Open its connection form and read the credential requirements. Choose permissions that cover the operations you intend to use.
2. Name the account clearly.Use a name that identifies its purpose, such as your test or operations account, so workflow authors can select it correctly.
3. Complete the credential fields.For services that support an authorization flow, use the displayed authorization action. Otherwise, supply the fields requested by the provider form.
4. Read the saved result.A provider connection is Verified only after its check succeeds. Review any error even if the credentials were saved.

Some credential types, including generic HTTP and webhook credentials, show Configured. Read the form's explanation of what was checked. That status does not prove access to your intended endpoint or a successful webhook delivery.

Use the connection in a workflow

Open the workflow step, select the named account, choose an available operation, and map its required inputs. Test with a record you control. Inspect the run result and confirm the corresponding provider result, especially for actions that create, send, update, or delete.

Verification checks the account; it does not prove every operation is permitted. A resource can require additional scopes or access within the provider.

Ask someone else to connect

When a customer or a colleague outside the team holds the account, send them a link instead of asking for their key. In Integrations, choose Ask someone to connect, then New link. Pick the service, name the connection, add an optional note for them, and choose how long the link works: 1, 3, 7 or 14 days.

The link is shown once. Send it only to that person. They open it, type their own key or token, and NodeHub checks it with the service before saving it as this business's connection. You never see the value. A link works once, stops after 10 failed tries, and can be revoked while it waits. Services you connect by signing in to them (OAuth) cannot be requested this way; connect those from their card.

Update credentials and resolve errors

• Needs attention or UnverifiedRead the error and check the credential, provider permissions, account access, and service availability. Recheck after correcting the cause.
• An account is missing from a stepConfirm the active business, required provider, connection status, and selected operation.
• A saved field looks emptySaved secret values are not returned to the form. Leave a configured field blank to retain its saved value, or enter a replacement and verify again.

Credentials are encrypted on the server. Keep API keys and passwords in Connections, separate from workflow text, data tables, and variables.