A plug that signs in to another system declares what it needs in its auth field. Collabase draws the matching form when someone creates a connection, stores the values encrypted and hands the connection of the running step to the action or trigger as context.auth.
The types
Use the credentials
httpClient and HttpMethod come from @collabase/plug-framework/common. The helpers retry the request and parse the answer.
OAuth
An OAuth plug needs an OAuth app for its provider, which an administrator registers once under Administration, Automation, OAuth apps. A person then selects Connect with the provider in the connection form. Collabase renews the token shortly before a step if it expires within five minutes. See OAuth apps.
Rules
- A connection is the credential of the step that runs. A plug never sees the connections of another step or another workspace.
- Credentials never appear in a run log: Collabase hides every value of the connection in the log of the step, even when the plug echoes it.
- Do not put a credential into an error message. Error messages reach the run log.
- A connection that stops working is marked Invalid and the admins of the workspace are told. Throw an error with a clear message when the other system refuses the credentials.
Last modified on October 26, 2026