March 27, 2026
AgentKit

Atlassian Jira and Confluence: one connector config routes to any customer instance automatically

Every Atlassian Cloud customer runs their own instance at a unique subdomain. Scalekit now resolves the instance URL dynamically at proxy time — one connector config routes correctly across all your enterprise customers.

Every Atlassian Cloud customer runs their own instance at a unique subdomain. Without dynamic instance URL resolution, a single connector config couldn't route correctly across multiple enterprise customers. Now it can.

Atlassian Dynamic Routing

An agent that auto-triages GitHub issues by creating corresponding Jira tickets connects to different customer instances dynamically. When Acme Corp's agent runs, the proxy resolves to acme.atlassian.net. When Beta Industries runs theirs, it routes to beta-industries.atlassian.net. Same connector config. No per-customer provisioning.

What's included

  • Pre-run hook resolves the correct Atlassian instance URL at proxy time using connected account metadata.
  • Single connector config works across unlimited Atlassian tenants — no per-customer duplication.
  • Sets the pattern for any connector where the API base URL varies by customer.
  • Works for both Jira and Confluence across Atlassian Cloud deployments.
Share on

Atlassian Jira and Confluence: one connector config routes to any customer instance automatically

Every Atlassian Cloud customer runs their own instance at a unique subdomain. Without dynamic instance URL resolution, a single connector config couldn't route correctly across multiple enterprise customers. Now it can.

Atlassian Dynamic Routing

An agent that auto-triages GitHub issues by creating corresponding Jira tickets connects to different customer instances dynamically. When Acme Corp's agent runs, the proxy resolves to acme.atlassian.net. When Beta Industries runs theirs, it routes to beta-industries.atlassian.net. Same connector config. No per-customer provisioning.

What's included

  • Pre-run hook resolves the correct Atlassian instance URL at proxy time using connected account metadata.
  • Single connector config works across unlimited Atlassian tenants — no per-customer duplication.
  • Sets the pattern for any connector where the API base URL varies by customer.
  • Works for both Jira and Confluence across Atlassian Cloud deployments.
Schedule a demo with Scalekit today.