Skip to main content

Structure

Multiple authentication methods per connector are allowed.

Properties

Authentication methods the connector supports.
FieldDescriptionTypeRequired
authorizationRuntime authorization strategy applied to outgoing requests.unionYes
certificatesMutual-TLS certificates and keys for this method.objectNo
configFieldsCredentials the end-user enters when linking an account.arrayNo
configNoticesCallouts shown while entering config fields.object[]No
environmentsDeployment targets selectable for this method.object[]Yes
grantTypeOAuth grant flow used to obtain tokens.
Allowed: authorization_code, client_credentials
Default: authorization_code
enumNo
labelDisplay name for this authentication method.stringYes
refreshAuthenticationConfiguration for refreshing expired credentials.objectNo
releaseStageMaturity level of this authentication method. Defaults to the highest stage among the actions and events it can run.
Allowed: preview, beta, ga, deprecated, internal
enumNo
requiredScopesScope names required by this authentication method. Space-separated, with any name that contains spaces wrapped in double quotes.stringNo
setupFieldsCredentials entered when creating a Connector Profile.arrayNo
setupNoticesCallouts shown while entering setup fields.object[]No
supportHelp resources shown while connecting with this method.objectNo
testActionsActions run to validate a connection after authentication.object[]No
typeSelects the OAuth 2.0 authentication method.stringYes
authorizationFlowMCP OAuth authorization flow; static credentials are used when omitted.objectNo
The variants share a common set of fields and are told apart by type.
The grantType field selects the OAuth grant flow, either authorization_code (default) or client_credentials.

authorization

Runtime authorization strategy applied to outgoing requests.
FieldDescriptionTypeRequired
redirectUriOAuth callback URL carried as connect-time metadata. Not used when authorizing requests.stringNo
signingOptional request signing applied to outgoing requests. Selects AWS SigV4 or HMAC signing.unionNo
typeSends requests without an authorization header.stringYes
Optional request signing applied to outgoing requests. Selects AWS SigV4 or HMAC signing.
FieldDescriptionTypeRequired
regionAWS region used in the signing credential scope. Falls back to the credential region or us-east-1 when omitted.stringNo
serviceAWS service name used in the signing credential scope. For example s3 or execute-api.stringYes
strategySigns requests with AWS Signature Version 4.stringYes
When the authorization type is oauth2, the runtime runs the authorization-code flow:
  1. The end-user clicks Connect in the StackOne Hub.
  2. The runtime builds the authorization URL from authorizationUrl and authorizationParams.
  3. The end-user signs in at the provider and grants access.
  4. The provider redirects back to the callback URL with an authorization code.
  5. The runtime exchanges that code for tokens at tokenUrl.
  6. The tokens are stored as the Linked Account’s credentials.
Examples

authorizationFlow

MCP OAuth authorization flow; static credentials are used when omitted.
FieldDescriptionTypeRequired
clientRegistrationClient registration mechanism used with the MCP server.
Allowed: cimd, dcr
Default: cimd
enumYes
discoveryWhether OAuth authorization-server metadata is discovered automatically.
Default: true
booleanYes
scopesOAuth scopes requested during the MCP authorization flow.string[]No
serverUrlMCP server URL the connect flow authorizes against.stringNo
Examples

certificates

Mutual-TLS certificates and keys for this method.
FieldDescriptionTypeRequired
certsClient certificates used for mutual-TLS.string[]No
keysPrivate keys used for mutual-TLS.string[]No
Examples

configFields

Credentials the end-user enters when linking an account.
FieldDescriptionTypeRequired
computedField value is a JEXL expression in value, evaluated at runtime rather than entered by the user.booleanNo
descriptionHelper text explaining what the user should enter.stringNo
externalSystemAccountIdentifierValue identifies the account in the external system, used to match incoming webhook events to a linked account.booleanNo
keyIdentifier the credential value is stored and referenced under.stringYes
labelHuman-readable name shown for this field.stringYes
placeholderExample value shown in the empty input to hint the expected format.stringNo
readOnlyWhether the field is displayed but cannot be edited by the user.
Default: false
booleanYes
requiredWhether the field must have a value.
Default: false
booleanYes
secretEncrypt the value at rest and mask it in the UI.
Default: false
booleanYes
tooltipAdditional guidance shown on hover for this field.stringNo
typeInput control rendered for this credential field.
Allowed: text, password, text_area
enumYes
validationClient-side validation constraint applied to the entered value.objectNo
valuePreset or computed value for the field, such as a fixed default or a JEXL expression.stringNo
Client-side validation constraint applied to the entered value.
FieldDescriptionTypeRequired
errorMessageMessage shown when the value fails the pattern or format check.stringNo
formatNamed format the entered value must match, standing in for a common regular expression. Provide this or pattern, not both.
Allowed: email, url, uri, uuid, date, datetime
enumNo
patternRegular expression the entered value must match. Provide this or format, not both.stringNo
Examples

configNotices

Callouts shown while entering config fields.
FieldDescriptionTypeRequired
anchorField key the notice is shown above. Only valid when position is top.stringNo
descriptionText shown in the notice.stringYes
keyIdentifier for the notice.stringYes
positionWhether the notice appears above or below the fields.
Allowed: top, bottom
Default: top
enumYes
typeVisual style of the notice.
Allowed: warning, info
Default: info
enumYes
Examples

environments

Deployment targets selectable for this method.
FieldDescriptionTypeRequired
keyIdentifier stored for the selected environment.stringYes
nameHuman-readable environment name.stringYes
Examples

refreshAuthentication

Configuration for refreshing expired credentials.
FieldDescriptionTypeRequired
actionAction executed to refresh the credentials.objectYes
scheduleCron expression for proactively refreshing credentials.stringNo
Action executed to refresh the credentials.Same fields as actions.
The initial OAuth exchange stores the provider’s refresh token in the Linked Account’s credentials. refreshAuthentication then keeps the access token current:
  1. On the schedule cron, the runtime runs the refresh_token action.
  2. The action sends the stored refresh token to the provider’s token endpoint.
  3. The provider returns a new access token, and sometimes a new refresh token.
  4. The returned tokens replace the Linked Account’s credentials.
Set schedule to fire before the access token expires, so requests never use a stale token.
Examples

setupFields

Credentials entered when creating a Connector Profile.
FieldDescriptionTypeRequired
computedField value is a JEXL expression in value, evaluated at runtime rather than entered by the user.booleanNo
descriptionHelper text explaining what the user should enter.stringNo
externalSystemAccountIdentifierValue identifies the account in the external system, used to match incoming webhook events to a linked account.booleanNo
keyIdentifier the credential value is stored and referenced under.stringYes
labelHuman-readable name shown for this field.stringYes
placeholderExample value shown in the empty input to hint the expected format.stringNo
readOnlyWhether the field is displayed but cannot be edited by the user.
Default: false
booleanYes
requiredWhether the field must have a value.
Default: false
booleanYes
secretEncrypt the value at rest and mask it in the UI.
Default: false
booleanYes
tooltipAdditional guidance shown on hover for this field.stringNo
typeInput control rendered for this credential field.
Allowed: text, password, text_area
enumYes
validationClient-side validation constraint applied to the entered value.objectNo
valuePreset or computed value for the field, such as a fixed default or a JEXL expression.stringNo
Client-side validation constraint applied to the entered value.
FieldDescriptionTypeRequired
errorMessageMessage shown when the value fails the pattern or format check.stringNo
formatNamed format the entered value must match, standing in for a common regular expression. Provide this or pattern, not both.
Allowed: email, url, uri, uuid, date, datetime
enumNo
patternRegular expression the entered value must match. Provide this or format, not both.stringNo
Examples

setupNotices

Callouts shown while entering setup fields.
FieldDescriptionTypeRequired
anchorField key the notice is shown above. Only valid when position is top.stringNo
descriptionText shown in the notice.stringYes
keyIdentifier for the notice.stringYes
positionWhether the notice appears above or below the fields.
Allowed: top, bottom
Default: top
enumYes
typeVisual style of the notice.
Allowed: warning, info
Default: info
enumYes
Examples

support

Help resources shown while connecting with this method.
FieldDescriptionTypeRequired
descriptionHelp text guiding the user through connecting.stringNo
guidesStep-by-step connection guides.objectNo
linkURL to external setup documentation. Defaults to the generated connector guide on docs.stackone.com when omitted.stringNo
Step-by-step connection guides.
FieldDescriptionTypeRequired
configGuide for the credentials end-users enter per connection.objectNo
setupGuide for the credentials your team registers once.objectNo
Guide for the credentials end-users enter per connection.
FieldDescriptionTypeRequired
sectionsOrdered sections making up the guide.object[]Yes
warningCautionary note shown at the top of the guide.stringNo
Ordered sections making up the guide.
FieldDescriptionTypeRequired
applicableScopesScope names for which this section is shown. Space-separated, with any name that contains spaces wrapped in double quotes.stringNo
contentIntroductory text for the section.stringYes
imageIllustrative image for the section.objectNo
listOrdered items elaborating the section.string[]No
stepsOrdered steps making up the section.object[]No
titleHeading for this guide section.stringYes
Illustrative image for the section.
FieldDescriptionTypeRequired
altAlternative text describing the image.stringYes
srcImage URL or a path relative to the connector.stringYes
Ordered steps making up the section.
FieldDescriptionTypeRequired
applicableScopesScope names for which this step is shown. Space-separated, with any name that contains spaces wrapped in double quotes.stringNo
contentBody text describing what the user should do.stringYes
displayScopesWhether the step shows badges for the actions its scopes unlock.booleanNo
imageIllustrative image for the step.objectNo
listOrdered items elaborating the step.string[]No
titleHeading for this guide step.stringYes
Illustrative image for the step.
FieldDescriptionTypeRequired
altAlternative text describing the image.stringYes
srcImage URL or a path relative to the connector.stringYes
Guide for the credentials your team registers once.
FieldDescriptionTypeRequired
sectionsOrdered sections making up the guide.object[]Yes
warningCautionary note shown at the top of the guide.stringNo
Ordered sections making up the guide.
FieldDescriptionTypeRequired
applicableScopesScope names for which this section is shown. Space-separated, with any name that contains spaces wrapped in double quotes.stringNo
contentIntroductory text for the section.stringYes
imageIllustrative image for the section.objectNo
listOrdered items elaborating the section.string[]No
stepsOrdered steps making up the section.object[]No
titleHeading for this guide section.stringYes
Illustrative image for the section.
FieldDescriptionTypeRequired
altAlternative text describing the image.stringYes
srcImage URL or a path relative to the connector.stringYes
Ordered steps making up the section.
FieldDescriptionTypeRequired
applicableScopesScope names for which this step is shown. Space-separated, with any name that contains spaces wrapped in double quotes.stringNo
contentBody text describing what the user should do.stringYes
displayScopesWhether the step shows badges for the actions its scopes unlock.booleanNo
imageIllustrative image for the step.objectNo
listOrdered items elaborating the step.string[]No
titleHeading for this guide step.stringYes
Illustrative image for the step.
FieldDescriptionTypeRequired
altAlternative text describing the image.stringYes
srcImage URL or a path relative to the connector.stringYes
Examples

testActions

Actions run to validate a connection after authentication.
FieldDescriptionTypeRequired
actionAction id or definition executed to test the connection.unionYes
conditionJEXL expression gating whether the test action runs.stringNo
requiredCurrently not in use.
Default: true
booleanYes
Action id or definition executed to test the connection.
A string value.
Examples

scopeDefinitions

Declare available scopes; profiles can pin requiredScopes.

baseUrl

Typically interpolates a $ here.

documentation

Connector-level external doc links, separate from per-auth guides.

Actions overview

Actions referenced by testActions and refresh_token must exist in actions[].