Integrations

An integration (the API calls it a connection) is your credentials for one app, stored encrypted in W6W. Once it exists, every Function, Endpoint and Workflow in your account can call that API, and none of your callers ever hold the API key, OAuth token or password themselves.

Integrations belong to your account, so every project in it can use them.

Before you start

The app you want must be registered with your W6W server. Most servers carry the official catalog, so search for it first. If you can’t find it, see Apps.

Add an integration

In the sidebar, under Connect, click Integrations.
Click + Add integration. The Add connection dialog opens.
Type in Search apps to connect…, or narrow the list with the category chips, and pick the app.
If the app supports more than one way to authenticate, choose one under Auth method.
Give it a Display name you’ll recognise, for example “Stripe (live)”.
Fill in the credential fields the app asks for, such as an API key, then click Save connection.
- For an OAuth app, click Sign in with <app> instead. A popup opens at the vendor; approve access there, and the popup closes itself.
- For an app that needs no credentials, click Use this.

How you know it worked: the new integration appears under Stored integrations. Click it: the banner at the top reads ✓ Connection is valid, followed by when it was last checked.

Check an integration

Click an integration in the list to open its page:

Test connection (top right) asks the vendor whether the stored credentials still work. The banner turns green when they do, or shows the vendor’s reason when they don’t.
The App card shows which app this is. ← Integrations goes back to the list.
Actions lists everything the app can do. A search box appears when there are more than ten. Click one to try it; see Test an action.
Recent runs shows the latest calls made through this integration.

Change or rotate credentials

On the Integrations list, click the pencil (edit) icon on the row.
In Edit connection, type only the values you want to change. A field you leave blank keeps its current value.
Click Save connection.

How you know it worked: open the integration and click Test connection. The banner reads ✓ Connection is valid.

For an OAuth integration there’s no re-authorise button. To sign in again (for example, to grant more permissions), add a new integration for the same app and point your steps at it.

Delete an integration

Click the bin icon on its row and confirm Delete connection. Anything that still uses it (a Function, a workflow step) fails until you point it at another integration.

Call it from code

Every call your code makes goes through W6W with your W6W token, never the vendor’s credentials. The integration’s id looks like conn_01H….

const env = await client.run({ urn: "conn_01H…", action: "send_email", payload: { to: "a@example.com" } });

See Node SDK.

w6w connections list
w6w run conn_01H… --action send_email --payload '{"to":"a@example.com"}'

See CLI.

Troubleshooting

Symptom	Cause	What to do
The app isn’t in Search apps to connect…	It isn’t registered on your server, or your organisation’s app policy hides it.	Register it under Apps, or ask your administrator.
`No integrations yet — add one above. You'll need a registered app first (see Apps)`	Your account has no integrations.	Click + Add integration.
`Popup blocked — allow popups for this site and try again.`	The browser blocked the OAuth popup.	Allow popups for your Studio address and click Sign in with <app> again.
The row shows an invalid tag, or the banner is red	The vendor rejected the stored credentials: a revoked key or an expired token.	Edit the integration with fresh credentials, or add a new one for an OAuth app.
`Permission denied by the provider — …` when you run an action	The credentials work but lack a scope or role that action needs.	Grant the permission at the vendor, or connect with an account that has it.

Where to next

Test an action: call one of the app’s actions and save the call as a test.
Apps: register an app your server doesn’t have yet.
Functions: give one of these actions a stable name your code calls.
Reliability: see how this API is performing.