{"templateId":"markdown","sharedDataIds":{"sidebar":"sidebar-guides/sidebars.yaml"},"props":{"metadata":{"markdoc":{"tagList":["admonition"]},"type":"markdown"},"seo":{"title":"Integrations","siteUrl":"https://docs.synqly.com","lang":"en-US","llmstxt":{"hide":false,"sections":[{"title":"Table of contents","includeFiles":["**/*"],"excludeFiles":[]}],"excludeFiles":[]}},"dynamicMarkdocComponents":[],"compilationErrors":[],"ast":{"$$mdtype":"Tag","name":"article","attributes":{},"children":[{"$$mdtype":"Tag","name":"Heading","attributes":{"level":1,"id":"integrations","__idx":0},"children":["Integrations"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["An Integration is the actual connection between an Account and a Provider."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["While Connectors define a common interface for interacting with a category of providers,"," ","Integrations represent the specific provider connection that has been configured and authenticated"," ","for a particular Account."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["For example, the Ticketing Connector defines how ticketing systems are accessed through Synqly."," ","An Integration represents a customer's actual connection to Jira, ServiceNow, or another"," ","supported ticketing provider."]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"why-integrations-exist","__idx":1},"children":["Why Integrations Exist"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Connectors and Providers alone are not enough to perform work."]},{"$$mdtype":"Tag","name":"Admonition","attributes":{"type":"info","name":"Bridging the gap"},"children":[{"$$mdtype":"Tag","name":"p","attributes":{},"children":["A Connector defines a common API, and a Provider defines a specific external system, but neither"," ","contains the customer-specific configuration, credentials, or authorization required to access"," ","that system."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Integrations bridge that gap by storing the information necessary to establish and maintain a"," ","connection to a Provider on behalf of an Account, allowing Connector API requests to be executed"," ","against the correct external system."]}]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"integrations-as-runtime-connections","__idx":2},"children":["Integrations as Runtime Connections"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["A useful way to think about an Integration is as a runtime instance of a Connector-Provider"," ","relationship."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["For example, two Accounts may both use Jira, but each requires its own authorization,"," ","configuration, and lifecycle management:"]},{"$$mdtype":"Tag","name":"Diagram","attributes":{"data-language":"mermaid","diagramType":"mermaid","diagramSource":"flowchart TD\n accA(Account A)\n accB(Account B)\n intA(Jira Integration)\n intB(Jira Integration)\n prov(Jira)\n\n accA --> intA\n accB --> intB\n intA & intB --> prov\n","diagramHtml":"

Account A

Account B

Jira Integration

Jira Integration

Jira

","diagramHtmlDark":"

Account A

Account B

Jira Integration

Jira Integration

Jira

"},"children":["flowchart TD\n accA(Account A)\n accB(Account B)\n intA(Jira Integration)\n intB(Jira Integration)\n prov(Jira)\n\n accA --> intA\n accB --> intB\n intA & intB --> prov\n"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Although both Integrations connect to the same Provider, they remain completely independent"," ","because they belong to different Accounts."]},{"$$mdtype":"Tag","name":"Admonition","attributes":{"type":"info","name":"Tenant isolation by design"},"children":[{"$$mdtype":"Tag","name":"p","attributes":{},"children":["This separation is fundamental to maintaining tenant isolation within Synqly. Data and"," ","credentials never cross Account boundaries."]}]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"integrations-and-integration-points","__idx":3},"children":["Integrations and Integration Points"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Integrations can optionally reference an Integration Point. In this relationship, the"," ","Integration Point defines shared requirements and governance rules, while the Integration"," ","represents the actual authorized connection that satisfies those requirements."]},{"$$mdtype":"Tag","name":"div","attributes":{"className":"md-table-wrapper"},"children":[{"$$mdtype":"Tag","name":"table","attributes":{"className":"md"},"children":[{"$$mdtype":"Tag","name":"thead","attributes":{},"children":[{"$$mdtype":"Tag","name":"tr","attributes":{},"children":[{"$$mdtype":"Tag","name":"th","attributes":{"data-label":"Concept"},"children":["Concept"]},{"$$mdtype":"Tag","name":"th","attributes":{"data-label":"Role"},"children":["Role"]}]}]},{"$$mdtype":"Tag","name":"tbody","attributes":{},"children":[{"$$mdtype":"Tag","name":"tr","attributes":{},"children":[{"$$mdtype":"Tag","name":"td","attributes":{},"children":[{"$$mdtype":"Tag","name":"strong","attributes":{},"children":["Integration Point"]}]},{"$$mdtype":"Tag","name":"td","attributes":{},"children":["Defines shared requirements and governance rules"]}]},{"$$mdtype":"Tag","name":"tr","attributes":{},"children":[{"$$mdtype":"Tag","name":"td","attributes":{},"children":[{"$$mdtype":"Tag","name":"strong","attributes":{},"children":["Integration"]}]},{"$$mdtype":"Tag","name":"td","attributes":{},"children":["The authorized connection that satisfies those rules"]}]},{"$$mdtype":"Tag","name":"tr","attributes":{},"children":[{"$$mdtype":"Tag","name":"td","attributes":{},"children":[{"$$mdtype":"Tag","name":"strong","attributes":{},"children":["Provider"]}]},{"$$mdtype":"Tag","name":"td","attributes":{},"children":["The external system the Integration connects to"]}]}]}]}]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["This allows Organizations to apply consistent policies across many Integrations without"," ","duplicating configuration."]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"the-full-picture","__idx":4},"children":["The Full Picture"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Integrations sit between Synqly's abstraction layer and the external systems where work occurs."]},{"$$mdtype":"Tag","name":"Diagram","attributes":{"data-language":"mermaid","diagramType":"mermaid","diagramSource":"flowchart TD\n conn(Connector)\n intg(Integration)\n prov(Provider)\n\n conn --> intg --> prov\n","diagramHtml":"

Connector

Integration

Provider

","diagramHtmlDark":"

Connector

Integration

Provider

"},"children":["flowchart TD\n conn(Connector)\n intg(Integration)\n prov(Provider)\n\n conn --> intg --> prov\n"]},{"$$mdtype":"Tag","name":"Admonition","attributes":{"type":"success","name":"The piece that makes it real"},"children":[{"$$mdtype":"Tag","name":"p","attributes":{},"children":["The Connector provides a unified interface, the Provider supplies the underlying functionality,"," ","and the Integration binds them together for a specific Account."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Without an Integration, a Connector is simply a common API and a Provider is simply an external"," ","system. The Integration is the object that makes the relationship active, authorized, and usable."]}]}]},"headings":[{"value":"Integrations","id":"integrations","depth":1},{"value":"Why Integrations Exist","id":"why-integrations-exist","depth":2},{"value":"Integrations as Runtime Connections","id":"integrations-as-runtime-connections","depth":2},{"value":"Integrations and Integration Points","id":"integrations-and-integration-points","depth":2},{"value":"The Full Picture","id":"the-full-picture","depth":2}],"frontmatter":{"slug":"guides/concepts/integrations","seo":{"title":"Integrations"}},"lastModified":"2026-07-02T06:20:08.000Z","pagePropGetterError":{"message":"","name":""}},"slug":"/guides/concepts/integrations","userData":{"isAuthenticated":false,"teams":["anonymous"]},"isPublic":true}