{"templateId":"markdown","sharedDataIds":{"sidebar":"sidebar-guides/sidebars.yaml"},"props":{"metadata":{"markdoc":{"tagList":["admonition"]},"type":"markdown"},"seo":{"title":"Integration Points","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":"integration-points","__idx":0},"children":["Integration Points"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Integration Points provide a reusable configuration and governance layer for Integrations."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["At first glance, it may seem simpler to configure each Integration individually. However, as the"," ","number of Accounts and Integrations grows, managing configuration on a per-Integration basis"," ","becomes difficult to maintain and govern consistently."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Integration Points solve this problem by allowing common integration requirements and policies"," ","to be defined once and reused across an Organization."]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"why-integration-points-exist","__idx":1},"children":["Why Integration Points Exist"]},{"$$mdtype":"Tag","name":"Admonition","attributes":{"type":"info","name":"Governance without repetition"},"children":[{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Integration Points separate integration governance from individual Integrations."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Rather than embedding configuration rules into every Integration, Organizations can define those"," ","rules centrally and apply them wherever needed. This promotes consistency while reducing"," ","duplication and administrative overhead."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Because Integration Points belong to the Organization rather than individual Accounts, the same"," ","configuration can be reused across multiple customers, tenants, or business units."]}]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"integration-points-as-governance-controls","__idx":2},"children":["Integration Points as Governance Controls"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["An Integration Point can define the requirements that an Integration must satisfy before it can"," ","be created or used."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["For example, an Organization may decide that only Jira and ServiceNow are approved ticketing"," ","providers. Instead of enforcing that rule separately for every Account, an Integration Point can"," ","define the approved provider list once and apply it consistently across all Accounts that"," ","reference it."]},{"$$mdtype":"Tag","name":"Diagram","attributes":{"data-language":"mermaid","diagramType":"mermaid","diagramSource":"flowchart TD\n ip[\"Approved Ticketing Providers (Integration Point)\"]\n jira(Jira ✓)\n snow(ServiceNow ✓)\n zen(Zendesk ✗)\n\n ip --> jira & snow & zen\n","diagramHtml":"

Approved Ticketing Providers (Integration Point)

Jira ✓

ServiceNow ✓

Zendesk ✗

","diagramHtmlDark":"

Approved Ticketing Providers (Integration Point)

Jira ✓

ServiceNow ✓

Zendesk ✗

"},"children":["flowchart TD\n ip[\"Approved Ticketing Providers (Integration Point)\"]\n jira(Jira ✓)\n snow(ServiceNow ✓)\n zen(Zendesk ✗)\n\n ip --> jira & snow & zen\n"]},{"$$mdtype":"Tag","name":"Admonition","attributes":{"type":"info","name":"Rules inherit automatically"},"children":[{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Any Integration associated with that Integration Point automatically inherits those requirements"," ","— no per-Account configuration needed."]}]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"integration-points-and-integrations","__idx":3},"children":["Integration Points and Integrations"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["A useful way to think about the relationship: an Integration Point defines the rules, while an"," ","Integration represents the actual connection to a Provider."]},{"$$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 the rules and requirements centrally"]}]},{"$$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 live connection that must satisfy 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 separation allows Organizations to manage integration standards centrally while still"," ","giving individual Accounts the flexibility to create and operate their own Integrations."]},{"$$mdtype":"Tag","name":"Admonition","attributes":{"type":"success","name":"Scaling with consistency"},"children":[{"$$mdtype":"Tag","name":"p","attributes":{},"children":["As Organizations scale, Integration Points become an important mechanism for maintaining"," ","consistency, reducing configuration drift, and ensuring that integrations adhere to"," ","organizational requirements without requiring manual oversight."]}]}]},"headings":[{"value":"Integration Points","id":"integration-points","depth":1},{"value":"Why Integration Points Exist","id":"why-integration-points-exist","depth":2},{"value":"Integration Points as Governance Controls","id":"integration-points-as-governance-controls","depth":2},{"value":"Integration Points and Integrations","id":"integration-points-and-integrations","depth":2}],"frontmatter":{"slug":"guides/getting-started/concepts/integration-points","seo":{"title":"Integration Points"}},"lastModified":"2026-06-11T11:53:23.000Z","pagePropGetterError":{"message":"","name":""}},"slug":"/guides/getting-started/concepts/integration-points","userData":{"isAuthenticated":false,"teams":["anonymous"]},"isPublic":true}