TownsifyDocs
Open console
Console page

Connection

Connection detail shows one selected service. Overview contains its status and credential source; Credentials and Resources configure authentication and allowed targets.

Console address
/townships/:townshipId/integrations/connections/:connectionId/:section
Console section
Township · Integrations
Reviewed
14 October 2026
On this page
Connection in the Townsify console, shown with illustrative dataOpen full size
Illustrative dataConnection. Captured from the running console.

Controls and behaviour

Provider-specific forms expose only that provider's fields. Test checks connectivity. The GitHub overview also contains optional repository defaults, while its Webhook section configures routing. Connector services use their declared authentication and scope controls.

Access and limits

A valid connection is only one part of access. An agent still needs a grant and compatible permission. Changing a credential can make an authorised provider-bound mission stale, requiring another authorisation.

Field reference

Field or stateValueMeaning
OverviewConnection stateStatus, credential source and last error. GitHub also has optional repository defaults.
CredentialsProvider formStores encrypted credentials. Test can contact the provider.
ResourcesResource scopeRestricts targets where supported.
WebhookProvider sectionShown for supported services. Routing and authentication are explicit configuration.

Need more help?

Open Mysaria from the console header to ask about the page you're on, or send work to an agent in your township.