{
  "name": "IntegrateStack Verified Integration Facts",
  "description": "Native integration facts for pairs of SaaS tools. Each entry was checked against vendor documentation and carries its source URLs and the date it was checked. A pair that is absent has not been verified; absence is not a statement that no integration exists.",
  "url": "https://integratestack.com/data",
  "version": "2026.11.11",
  "date_modified": "2026-11-11",
  "license": "pending",
  "license_url": "",
  "citation": "IntegrateStack (2026). Verified Integration Facts, version 2026.11.11 [Data set]. https://integratestack.com/data",
  "schema": {
    "pair": "Sorted slug pair \"a__b\"; tool_a is the alphabetically first slug.",
    "status": "\"native\" or \"no_native\". \"no_native\" is used only when vendor documentation confirms the absence.",
    "direction": "\"a_to_b\", \"b_to_a\" or \"both\": which way data moves between tool_a and tool_b. Empty for no_native.",
    "data_flows_from": "Slug the data leaves, for one-way integrations. Empty when direction is \"both\".",
    "checked": "Date (YYYY-MM-DD) the entry was last checked against source_urls."
  },
  "count": 123,
  "facts": [
    {
      "pair": "activecampaign__calendly",
      "tool_a": "activecampaign",
      "tool_a_name": "ActiveCampaign",
      "tool_b": "calendly",
      "tool_b_name": "Calendly",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "calendly",
      "data_flows_to": "activecampaign",
      "mechanism": "ActiveCampaign Calendly integration",
      "what_syncs": [
        "Booked, changed and canceled meetings",
        "Deals created or updated",
        "Tags by event type",
        "Booking answers to custom fields and list membership"
      ],
      "plan_requirements": "ActiveCampaign Plus, Pro or Enterprise and a paid Calendly plan.",
      "notes": "Past bookings are not imported.",
      "source_urls": [
        "https://www.activecampaign.com/apps/calendly"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#activecampaign__calendly"
    },
    {
      "pair": "activecampaign__hubspot",
      "tool_a": "activecampaign",
      "tool_a_name": "ActiveCampaign",
      "tool_b": "hubspot",
      "tool_b_name": "HubSpot",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "ActiveCampaign data sync app by HubSpot",
      "what_syncs": [
        "Contacts",
        "ActiveCampaign accounts with HubSpot companies",
        "Deals"
      ],
      "plan_requirements": "ActiveCampaign Lite, Plus, Professional or Enterprise. Custom field mappings need Data Hub Starter or higher.",
      "notes": "Built by HubSpot.",
      "source_urls": [
        "https://ecosystem.hubspot.com/marketplace/apps/activecampaign-data-sync"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#activecampaign__hubspot"
    },
    {
      "pair": "activecampaign__shopify",
      "tool_a": "activecampaign",
      "tool_a_name": "ActiveCampaign",
      "tool_b": "shopify",
      "tool_b_name": "Shopify",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "shopify",
      "data_flows_to": "activecampaign",
      "mechanism": "ActiveCampaign Marketing app for Shopify",
      "what_syncs": [
        "Real-time store data sent to ActiveCampaign",
        "Abandoned cart data for emails",
        "Purchase data for post-purchase messaging",
        "Product catalog for marketing emails"
      ],
      "plan_requirements": "ActiveCampaign Starter tier or higher. Product catalog, coupons block, and ecommerce dashboard are listed from Plus; a Shopify Plus integration feature is listed from Pro.",
      "notes": "The app is developed by ActiveCampaign. The listing does not name the exact fields synced or describe any data written back to Shopify.",
      "source_urls": [
        "https://apps.shopify.com/activecampaign"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#activecampaign__shopify"
    },
    {
      "pair": "activecampaign__stripe",
      "tool_a": "activecampaign",
      "tool_a_name": "ActiveCampaign",
      "tool_b": "stripe",
      "tool_b_name": "Stripe",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "stripe",
      "data_flows_to": "activecampaign",
      "mechanism": "ActiveCampaign Stripe integration",
      "what_syncs": [
        "Stripe customers, orders and subscriptions",
        "Order status changes, refunds and failed invoices for automations",
        "Contact tags"
      ],
      "plan_requirements": "Plus, Pro or Enterprise per ActiveCampaign's app page (its help center also lists Starter).",
      "notes": "",
      "source_urls": [
        "https://www.activecampaign.com/apps/stripe"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#activecampaign__stripe"
    },
    {
      "pair": "airtable__slack",
      "tool_a": "airtable",
      "tool_a_name": "Airtable",
      "tool_b": "slack",
      "tool_b_name": "Slack",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "airtable",
      "data_flows_to": "slack",
      "mechanism": "Airtable Slack automation actions and Slack notifications",
      "what_syncs": [
        "Formatted Slack messages from automations, with record fields, links and mentions, to a channel, DM or thread",
        "Actionable Slack messages with buttons that update the Airtable record",
        "Base, record and view change notifications posted to a Slack channel"
      ],
      "plan_requirements": "Available on all Airtable plans; automation run limits vary by plan.",
      "notes": "Mainly Airtable to Slack. Actionable-message buttons write back to the record, need Editor access or higher, and expire after 7 days. Airtable has no outbound HTTP automation action; webhooks require a script step.",
      "source_urls": [
        "https://support.airtable.com/articles/7283239511-airtable-automation-actions-slack",
        "https://support.airtable.com/articles/9647929364-receiving-base-activity-notifications-in-slack"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#airtable__slack"
    },
    {
      "pair": "amazon__shopify",
      "tool_a": "amazon",
      "tool_a_name": "Amazon",
      "tool_b": "shopify",
      "tool_b_name": "Shopify",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Shopify Marketplace Connect app (by Shopify, formerly Codisto)",
      "what_syncs": [
        "Product catalog listed on Amazon",
        "Product and order changes synced to marketplaces",
        "Inventory sync",
        "Prices converted to the marketplace currency",
        "Amazon orders imported into the Shopify admin to fulfill there (all orders, or only merchant-fulfilled ones)",
        "Tracking sent back to the marketplace"
      ],
      "plan_requirements": "Free to install; the first 50 marketplace-synced orders per month are free, then a 1% fee per additional synced order, capped at $99 per month.",
      "notes": "Built by Shopify. Product, price and inventory changes go from Shopify to the marketplace, and marketplace orders are imported into Shopify. Orders that miss the automatic import can be imported by hand.",
      "source_urls": [
        "https://help.shopify.com/en/manual/online-sales-channels/marketplace-connect",
        "https://apps.shopify.com/marketplace-connect",
        "https://help.shopify.com/en/manual/online-sales-channels/marketplace-connect/manage-orders/import"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#amazon__shopify"
    },
    {
      "pair": "asana__drata",
      "tool_a": "asana",
      "tool_a_name": "Asana",
      "tool_b": "drata",
      "tool_b_name": "Drata",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Drata Asana connection",
      "what_syncs": [
        "Security tagged Asana tasks read as evidence",
        "Severity labels mapped to Drata severity levels",
        "Asana tickets created and updated from Drata"
      ],
      "plan_requirements": "Admin access to the organization's Asana account. Creating and updating tickets requires Write Access on the connection. Drata role of Admin, Information Security Lead, DevOps Engineer, or Workspace Manager.",
      "notes": "The security tag defaults to Security and must match the label used in the Asana workspace. Severity labels can be remapped on the connection page.",
      "source_urls": [
        "https://help.drata.com/en/articles/5008063-asana-integration-guide",
        "https://help.drata.com/en/articles/7968908-create-tickets-for-asana"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#asana__drata"
    },
    {
      "pair": "asana__jira",
      "tool_a": "asana",
      "tool_a_name": "Asana",
      "tool_b": "jira",
      "tool_b_name": "Jira",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Asana Jira Cloud integration",
      "what_syncs": [
        "Two-way sync of tasks and Jira issues",
        "Designated fields on tasks and issues",
        "Comments",
        "Jira issues created from Asana tasks via Rules",
        "Existing Jira issues linked to tasks"
      ],
      "plan_requirements": "Asana Business and Enterprise for full access. Premium has limited access, such as creating Asana tasks from Jira issues and the Jira widget on a task.",
      "notes": "The listing is marked as made by Asana. Sync direction is set per project and can be Asana to Jira, Jira to Asana, or both.",
      "source_urls": [
        "https://asana.com/apps/jira"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#asana__jira"
    },
    {
      "pair": "asana__slack",
      "tool_a": "asana",
      "tool_a_name": "Asana",
      "tool_b": "slack",
      "tool_b_name": "Slack",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Asana for Slack",
      "what_syncs": [
        "Tasks created from Slack messages, a memo emoji reaction or the /asana command",
        "Tasks completed, assigned, commented on, scheduled and added to projects from Slack",
        "Task created and completed updates posted to channels linked to a project"
      ],
      "plan_requirements": "No plan requirement stated by Asana.",
      "notes": "",
      "source_urls": [
        "https://asana.com/apps/slack"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#asana__slack"
    },
    {
      "pair": "ashby__bamboohr",
      "tool_a": "ashby",
      "tool_a_name": "Ashby",
      "tool_b": "bamboohr",
      "tool_b_name": "BambooHR",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "ashby",
      "data_flows_to": "bamboohr",
      "mechanism": "Ashby BambooHR integration",
      "what_syncs": [
        "Hired candidate name, email, and phone",
        "LinkedIn profile, salary, and start date",
        "Job Information and stock option custom fields",
        "Resumes and offer letters"
      ],
      "plan_requirements": "Available on all Ashby plans, with custom fields not available on Foundations; Organization Admin in Ashby to configure; BambooHR API key from a user with at least Full Admin access.",
      "notes": "Automatic push on hire can be enabled only after one candidate has been pushed manually. Start dates cannot be updated in BambooHR after the push, and files other than resumes and offer letters are not sent.",
      "source_urls": [
        "https://docs.ashbyhq.com/bamboohr"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#ashby__bamboohr"
    },
    {
      "pair": "ashby__docusign",
      "tool_a": "ashby",
      "tool_a_name": "Ashby",
      "tool_b": "docusign",
      "tool_b_name": "DocuSign",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "ashby",
      "data_flows_to": "docusign",
      "mechanism": "Ashby DocuSign integration",
      "what_syncs": [
        "Offer e-signature requests sent through DocuSign",
        "Other e-signature documents sent through DocuSign",
        "Mapped Ashby values in DocuSign custom fields",
        "Request status visible in Ashby offer details"
      ],
      "plan_requirements": "DocuSign Standard plan or above, with custom fields typically on Business Pro and above; setup by an Ashby admin.",
      "notes": "Documents are processed and stored in the selected DocuSign account, and request status can be tracked in Ashby. Edits must be made in the preview editor for each request and do not carry over.",
      "source_urls": [
        "https://docs.ashbyhq.com/docusign"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#ashby__docusign"
    },
    {
      "pair": "ashby__rippling",
      "tool_a": "ashby",
      "tool_a_name": "Ashby",
      "tool_b": "rippling",
      "tool_b_name": "Rippling",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "ashby",
      "data_flows_to": "rippling",
      "mechanism": "Ashby app in Rippling",
      "what_syncs": [
        "Hired candidate name, email, phone, salary and start date",
        "Optional offer fields: department, equity shares, job title, signing bonus and work location",
        "Offer letters"
      ],
      "plan_requirements": "Not stated in Ashby's integration doc.",
      "notes": "Pushed with Add to Rippling on a Hired candidate, or automatically once the HRIS auto-push setting is on (it requires one earlier manual push). The person arrives in Rippling as a candidate and still needs the Hire step there. File uploads do not sync, and a pushed candidate cannot be pushed again.",
      "source_urls": [
        "https://docs.ashbyhq.com/rippling"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#ashby__rippling"
    },
    {
      "pair": "ashby__slack",
      "tool_a": "ashby",
      "tool_a_name": "Ashby",
      "tool_b": "slack",
      "tool_b_name": "Slack",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Ashby Slack integration (Ashby bot)",
      "what_syncs": [
        "Ashby notifications sent by DM or channel",
        "Alerts and scheduled dashboards",
        "Interviewer reminders",
        "Private interview channels created and archived",
        "Slack replies saved to candidate notes",
        "Replies to candidate texts sent from Slack"
      ],
      "plan_requirements": "Included in the Ashby subscription at no additional fee; Slack workspace admin rights to enable; each user turns on Slack notifications in personal settings.",
      "notes": "Slack notifications are off by default per user. Private interview channels cannot be enabled globally and are created only for booked interviews, and Slack webhooks are not supported.",
      "source_urls": [
        "https://docs.ashbyhq.com/slack"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#ashby__slack"
    },
    {
      "pair": "auth0__vanta",
      "tool_a": "auth0",
      "tool_a_name": "Auth0",
      "tool_b": "vanta",
      "tool_b_name": "Vanta",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "auth0",
      "data_flows_to": "vanta",
      "mechanism": "Vanta Auth0 integration",
      "what_syncs": [
        "Auth0 account data",
        "Accounts matched to current employees",
        "Accounts flagged for deprovisioning after offboarding"
      ],
      "plan_requirements": "",
      "notes": "Listed under identity providers and built by Vanta. The listing shows no supported resources list and describes no writes to Auth0.",
      "source_urls": [
        "https://www.vanta.com/integrations/auth0"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#auth0__vanta"
    },
    {
      "pair": "bamboohr__drata",
      "tool_a": "bamboohr",
      "tool_a_name": "BambooHR",
      "tool_b": "drata",
      "tool_b_name": "Drata",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "bamboohr",
      "data_flows_to": "drata",
      "mechanism": "Drata BambooHR connection",
      "what_syncs": [
        "Employee names and work email addresses",
        "Hire dates and separation dates",
        "Employment status and job information",
        "Signed documents and policies (optional)"
      ],
      "plan_requirements": "BambooHR admin access to create a custom view-only access level. Connection uses OAuth (must be enabled for the tenant) or an API key.",
      "notes": "Read-only. Drata recommends a read-only administrator service account with access limited to the listed fields and Company Files folders.",
      "source_urls": [
        "https://help.drata.com/en/articles/5122726-bamboohr-integration-guide"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#bamboohr__drata"
    },
    {
      "pair": "bamboohr__greenhouse",
      "tool_a": "bamboohr",
      "tool_a_name": "BambooHR",
      "tool_b": "greenhouse",
      "tool_b_name": "Greenhouse",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "greenhouse",
      "data_flows_to": "bamboohr",
      "mechanism": "Greenhouse Recruiting BambooHR integration",
      "what_syncs": [
        "Hired candidate name, emails, and phone numbers",
        "Start date, job title, department, and office",
        "Resume, cover letter, and offer letter",
        "Offer employment type",
        "Optional salary, birth date, hourly rate, contract value"
      ],
      "plan_requirements": "Greenhouse Core, Plus, or Pro subscription tiers; a BambooHR API key and subdomain from a user whose access level can add new employees and edit the exported fields and the Documents tab.",
      "notes": "Export is manual and per candidate when marking them as hired; bulk export is not possible. Department and office values must match BambooHR exactly, and job titles export only if they already exist there.",
      "source_urls": [
        "https://support.greenhouse.io/hc/en-us/articles/201177624-BambooHR-integration"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#bamboohr__greenhouse"
    },
    {
      "pair": "bamboohr__vanta",
      "tool_a": "bamboohr",
      "tool_a_name": "BambooHR",
      "tool_b": "vanta",
      "tool_b_name": "Vanta",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "bamboohr",
      "data_flows_to": "vanta",
      "mechanism": "Vanta BambooHR integration",
      "what_syncs": [
        "Employee status, first and last name, and work and home email",
        "Hire date, employment status and employment status date",
        "Job title, department and manager",
        "Time off, used to mark people on leave"
      ],
      "plan_requirements": "A BambooHR user with Full Admin or a custom access level granting View Only on the listed fields. The connection uses OAuth and the connecting user must be signed in to BambooHR.",
      "notes": "Read-only. Vanta imports active employees and those terminated after a date you choose. Profiles match Vanta people by email; unmatched ones appear under Merge HR data. If the connecting user leaves the company, the connection has to be redone.",
      "source_urls": [
        "https://help.vanta.com/en/articles/11345684-connecting-vanta-bamboo-hr",
        "https://www.vanta.com/integrations/bamboohr"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#bamboohr__vanta"
    },
    {
      "pair": "bigcommerce__hubspot",
      "tool_a": "bigcommerce",
      "tool_a_name": "BigCommerce",
      "tool_b": "hubspot",
      "tool_b_name": "HubSpot",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "BigCommerce data sync app by HubSpot",
      "what_syncs": [
        "BigCommerce customers with HubSpot contacts",
        "Orders, without line items",
        "Products"
      ],
      "plan_requirements": "A BigCommerce subscription is required. Custom field mappings need Data Hub Starter or higher.",
      "notes": "Built by HubSpot. The listing does not state a sync direction per object, so order sync direction is unconfirmed.",
      "source_urls": [
        "https://ecosystem.hubspot.com/marketplace/apps/bigcommerce-data-sync"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#bigcommerce__hubspot"
    },
    {
      "pair": "calendly__hubspot",
      "tool_a": "calendly",
      "tool_a_name": "Calendly",
      "tool_b": "hubspot",
      "tool_b_name": "HubSpot",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "calendly",
      "data_flows_to": "hubspot",
      "mechanism": "Calendly HubSpot integration (built by Calendly)",
      "what_syncs": [
        "Invitees to contacts",
        "Events to meeting engagements",
        "Booking answers to contact properties",
        "Contact owner and company"
      ],
      "plan_requirements": "Calendly Standard or higher. HubSpot tier not stated; workflows need Professional.",
      "notes": "",
      "source_urls": [
        "https://ecosystem.hubspot.com/marketplace/listing/calendly-199720",
        "https://calendly.com/pricing"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#calendly__hubspot"
    },
    {
      "pair": "calendly__mailchimp",
      "tool_a": "calendly",
      "tool_a_name": "Calendly",
      "tool_b": "mailchimp",
      "tool_b_name": "Mailchimp",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "calendly",
      "data_flows_to": "mailchimp",
      "mechanism": "Calendly Mailchimp integration",
      "what_syncs": [
        "Invitees added to a Mailchimp audience with tags by rule",
        "Booked, canceled and rescheduled events in the contact activity feed"
      ],
      "plan_requirements": "Calendly Standard or higher; any Mailchimp plan with an admin connecting.",
      "notes": "Invitees in GDPR countries are added as transactional contacts.",
      "source_urls": [
        "https://calendly.com/help/calendly-mailchimp"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#calendly__mailchimp"
    },
    {
      "pair": "canvas-lms__google-drive",
      "tool_a": "canvas-lms",
      "tool_a_name": "Canvas LMS",
      "tool_b": "google-drive",
      "tool_b_name": "Google Drive",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "google-drive",
      "data_flows_to": "canvas-lms",
      "mechanism": "Google Assignments LTI",
      "what_syncs": [
        "Drive files attached to Canvas assignments",
        "Student submissions made from Google Drive",
        "Grades synced to the Canvas gradebook"
      ],
      "plan_requirements": "Google Workspace for Education for the organization, with an account for each instructor or TA; an LMS that supports LTI 1.1 or higher; setup may need the LMS administrator.",
      "notes": "Grade sync is one way from Assignments to the LMS, and only the most recent grade syncs after a regrade. Group assignments and peer review are not built in.",
      "source_urls": [
        "https://support.google.com/edu/assignments/answer/9069281?hl=en"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#canvas-lms__google-drive"
    },
    {
      "pair": "canvas-lms__microsoft-teams",
      "tool_a": "canvas-lms",
      "tool_a_name": "Canvas LMS",
      "tool_b": "microsoft-teams",
      "tool_b_name": "Microsoft Teams",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "canvas-lms",
      "data_flows_to": "microsoft-teams",
      "mechanism": "Microsoft Teams Sync and Microsoft Teams LTI apps for Canvas",
      "what_syncs": [
        "Class teams created in Teams from Canvas course enrollments",
        "Canvas users matched to Microsoft Entra ID users by a chosen login attribute",
        "Teams meetings scheduled from a Canvas course (Teams Meetings LTI)"
      ],
      "plan_requirements": "Microsoft Education license (A1 or higher) on a single Microsoft tenant. A Canvas admin enables the developer keys and Teams Sync; a Microsoft tenant admin who can approve apps grants consent.",
      "notes": "One Canvas field (email, login ID, SIS user ID or integration ID) must exactly match one Entra field (UPN, primary email or email alias), with an optional domain suffix. Schools using School Data Sync must turn off SDS team creation and run a group cleanup first. Teams Meetings LTI works without Course Sync but then loses Add entire class.",
      "source_urls": [
        "https://learn.microsoft.com/en-us/microsoft-365/lti/teams-classes-with-canvas?view=o365-worldwide",
        "https://learn.microsoft.com/en-us/microsoft-365/lti/teams-meetings-with-canvas?view=o365-worldwide"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#canvas-lms__microsoft-teams"
    },
    {
      "pair": "canvas-lms__zoom",
      "tool_a": "canvas-lms",
      "tool_a_name": "Canvas LMS",
      "tool_b": "zoom",
      "tool_b_name": "Zoom",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "zoom",
      "data_flows_to": "canvas-lms",
      "mechanism": "Zoom LTI Pro",
      "what_syncs": [
        "Zoom meetings scheduled and started from within a Canvas course",
        "Zoom cloud recordings available to students in the course",
        "Meeting attendance sent to the Canvas gradebook as an AttendanceReport-YYYY-MM-DD assignment (LTI Pro 1.3)"
      ],
      "plan_requirements": "Zoom Education, Business or Enterprise plan; a Zoom account owner or admin to install it; a Canvas admin to enable the LTI Advantage gradebook permissions on the LTI Pro developer key.",
      "notes": "Attendance grades only count students signed in to the Zoom account (or via external authentication) with the same email as Canvas. No report for meetings under 5 minutes, meetings starting over 10 minutes late, Join Before Host, personal meeting IDs, or alternative hosts unless the host joins.",
      "source_urls": [
        "https://marketplace.zoom.us/apps/f8JUB3eeQv2lXsjKq5B2FA",
        "https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0064543"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#canvas-lms__zoom"
    },
    {
      "pair": "clickup__drata",
      "tool_a": "clickup",
      "tool_a_name": "ClickUp",
      "tool_b": "drata",
      "tool_b_name": "Drata",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Drata ClickUp connection",
      "what_syncs": [
        "ClickUp spaces, folders, lists, task types read",
        "ClickUp tasks and subtasks created from Drata",
        "Ticket status and assignee shown in Drata"
      ],
      "plan_requirements": "The Priority and Tags ClickApps must be enabled in the ClickUp workspace. Creating tasks requires Write Access on the connection. Only Drata Admins can configure the connection.",
      "notes": "Only tasks created from Drata controls, tests, or risks appear in Drata. Tasks created directly in ClickUp are not imported.",
      "source_urls": [
        "https://help.drata.com/en/articles/10105116-clickup-integration-guide"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#clickup__drata"
    },
    {
      "pair": "clickup__slack",
      "tool_a": "clickup",
      "tool_a_name": "ClickUp",
      "tool_b": "slack",
      "tool_b_name": "Slack",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "ClickUp for Slack",
      "what_syncs": [
        "Tasks created from the Create Task message shortcut or /clickup new",
        "Tasks edited from Slack",
        "Task notifications posted to channels"
      ],
      "plan_requirements": "No plan requirement stated; guests and limited members cannot use it.",
      "notes": "",
      "source_urls": [
        "https://clickup.com/integrations/slack"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#clickup__slack"
    },
    {
      "pair": "clickup__vanta",
      "tool_a": "clickup",
      "tool_a_name": "ClickUp",
      "tool_b": "vanta",
      "tool_b_name": "Vanta",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Vanta ClickUp integration",
      "what_syncs": [
        "ClickUp tasks created from Vanta",
        "Task status and priority tags tracked",
        "P0 to P3 security issue SLA checks",
        "ClickUp accounts compared against current employees"
      ],
      "plan_requirements": "",
      "notes": "Listed under task management and built by Vanta. Setup steps are in the Vanta help article Connecting Vanta & ClickUp.",
      "source_urls": [
        "https://www.vanta.com/integrations/clickup",
        "https://help.vanta.com/en/articles/14725622-connecting-vanta-clickup"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#clickup__vanta"
    },
    {
      "pair": "confluence__drata",
      "tool_a": "confluence",
      "tool_a_name": "Confluence",
      "tool_b": "drata",
      "tool_b_name": "Drata",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "confluence",
      "data_flows_to": "drata",
      "mechanism": "Drata Confluence connection (policy sync)",
      "what_syncs": [
        "Published Confluence policy pages imported into Drata",
        "Policies routed for approval and acknowledgement"
      ],
      "plan_requirements": "Administrative access to the Confluence spaces that hold the policy pages. Drata role of Admin, Workspace Manager, or DevOps Engineer.",
      "notes": "Only published pages in shared spaces sync. Drafts, personal or private spaces, pages with macros, and attachment files are not imported.",
      "source_urls": [
        "https://help.drata.com/en/articles/9293760-confluence-integration-guide"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#confluence__drata"
    },
    {
      "pair": "confluence__vanta",
      "tool_a": "confluence",
      "tool_a_name": "Confluence",
      "tool_b": "vanta",
      "tool_b_name": "Vanta",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "confluence",
      "data_flows_to": "vanta",
      "mechanism": "Vanta Confluence integration (policy sync and access)",
      "what_syncs": [
        "Published Confluence policy pages into Vanta",
        "Confluence accounts matched to active employees",
        "Accounts flagged for deprovisioning"
      ],
      "plan_requirements": "",
      "notes": "Only published policy pages are synced. The listing describes no writes back to Confluence.",
      "source_urls": [
        "https://www.vanta.com/integrations/confluence"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#confluence__vanta"
    },
    {
      "pair": "docusign__greenhouse",
      "tool_a": "docusign",
      "tool_a_name": "DocuSign",
      "tool_b": "greenhouse",
      "tool_b_name": "Greenhouse",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Greenhouse Recruiting Docusign integration",
      "what_syncs": [
        "Offer documents sent for e-signature",
        "Signature status shown on offer details",
        "Signed offer letter saved to candidate profile"
      ],
      "plan_requirements": "Works on any Docusign tier, with Business Pro recommended for full functionality; Greenhouse template editing needs the offer template management permission; each user completes their own setup.",
      "notes": "It works only for candidates in the offer stage and cannot be set up once for a whole organization. Each Docusign token must sit on its own line in the offer template.",
      "source_urls": [
        "https://support.greenhouse.io/hc/en-us/articles/205633569-Docusign-integration"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#docusign__greenhouse"
    },
    {
      "pair": "docusign__hubspot",
      "tool_a": "docusign",
      "tool_a_name": "DocuSign",
      "tool_b": "hubspot",
      "tool_b_name": "HubSpot",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "hubspot",
      "data_flows_to": "docusign",
      "mechanism": "HubSpot Docusign integration",
      "what_syncs": [
        "Envelopes created and sent from HubSpot records",
        "Mapped HubSpot properties prefill Docusign fields",
        "Envelopes tracked on contact, company and deal records"
      ],
      "plan_requirements": "Available on all HubSpot products and plans. Needs a paid Docusign plan and a Docusign Admin to connect. Custom property mapping needs Docusign eSignature Business Pro or higher.",
      "notes": "This is not a data sync app and does not copy full record details to Docusign. Each HubSpot user has to connect their own Docusign user.",
      "source_urls": [
        "https://knowledge.hubspot.com/integrations/use-hubspots-integration-with-docusign"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#docusign__hubspot"
    },
    {
      "pair": "docusign__salesforce",
      "tool_a": "docusign",
      "tool_a_name": "DocuSign",
      "tool_b": "salesforce",
      "tool_b_name": "Salesforce",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "salesforce",
      "data_flows_to": "docusign",
      "mechanism": "Docusign CLM for Salesforce (AppExchange package via Docusign Apps Launcher)",
      "what_syncs": [
        "Salesforce record data into Docusign CLM agreement templates"
      ],
      "plan_requirements": "Paid Docusign CLM licence; pricing is quote-based.",
      "notes": "Docusign's public pages do not detail which fields write back to Salesforce after signature. CLM is sold as part of Docusign's Intelligent Agreement Management platform.",
      "source_urls": [
        "https://www.docusign.com/integrations/clm-for-salesforce"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#docusign__salesforce"
    },
    {
      "pair": "drata__github",
      "tool_a": "drata",
      "tool_a_name": "Drata",
      "tool_b": "github",
      "tool_b_name": "GitHub",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "github",
      "data_flows_to": "drata",
      "mechanism": "Drata GitHub Issues connection; Drata GitHub version control connection",
      "what_syncs": [
        "GitHub issues carrying the security label",
        "Issue severity from Critical to Low labels",
        "Version control accounts and repository data",
        "Organization and repository rulesets"
      ],
      "plan_requirements": "GitHub organization owner access. In Drata, the Admin, Workspace Manager, or DevOps Engineer role is required to set up the connection.",
      "notes": "Drata reads from GitHub and does not change permissions there. Labels entered in Drata must match the labels used in GitHub.",
      "source_urls": [
        "https://help.drata.com/en/articles/4806987-github-issues-integration-guide",
        "https://help.drata.com/en/articles/13296062-manage-connected-version-control"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#drata__github"
    },
    {
      "pair": "drata__hubspot",
      "tool_a": "drata",
      "tool_a_name": "Drata",
      "tool_b": "hubspot",
      "tool_b_name": "HubSpot",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "hubspot",
      "data_flows_to": "drata",
      "mechanism": "Drata HubSpot connection (User Access Review)",
      "what_syncs": [
        "HubSpot users",
        "Assigned roles per user",
        "Access metadata for reviews"
      ],
      "plan_requirements": "HubSpot admin access and a HubSpot private app with read-only user scopes, whose access token is entered in Drata. Drata role of Admin, Workspace Manager, or DevOps Engineer.",
      "notes": "Read-only. Because of a HubSpot API limitation, a user must be both deactivated and deleted in HubSpot before Drata detects the removed access.",
      "source_urls": [
        "https://help.drata.com/en/articles/8987926-hubspot-integration-guide-uar"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#drata__hubspot"
    },
    {
      "pair": "drata__jira",
      "tool_a": "drata",
      "tool_a_name": "Drata",
      "tool_b": "jira",
      "tool_b_name": "Jira",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Drata Jira Cloud connection (with Ticket Automation)",
      "what_syncs": [
        "Jira users read for ownership and assignment",
        "Security issues read by label or JQL",
        "Projects and workflows read for evidence",
        "Jira issues created from controls, tests, risks",
        "Automated tickets for failed tests or controls"
      ],
      "plan_requirements": "Jira Admin access and permission to install and authorize apps. Writing needs the optional Write Access setting (update:jira-work scope) plus project-level permissions. Creating tickets in Drata needs the Admin or Information Security Lead role.",
      "notes": "The entry covers Jira Cloud. Jira Data Center connects separately, and ticket automation is supported for Jira Cloud only. Drata does not validate JQL queries and checks only the Priority field for severity.",
      "source_urls": [
        "https://help.drata.com/en/articles/4663378-jira-connection",
        "https://help.drata.com/en/articles/6953569-ticket-automation-jira-only",
        "https://help.drata.com/en/articles/6474482-create-and-map-jira-tickets-in-drata"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#drata__jira"
    },
    {
      "pair": "drata__linear",
      "tool_a": "drata",
      "tool_a_name": "Drata",
      "tool_b": "linear",
      "tool_b_name": "Linear",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Drata Linear connection",
      "what_syncs": [
        "Linear workspace issues read as vulnerability evidence",
        "Linear tickets created from controls, tests, risks"
      ],
      "plan_requirements": "Creating tickets requires Write Access enabled on the Linear connection. Drata role of Admin, Information Security Lead, DevOps Engineer, or Workspace Manager.",
      "notes": "The workspace to sync is chosen during authorization. Tickets created directly in the external tool are not imported into Drata's ticket view.",
      "source_urls": [
        "https://help.drata.com/en/articles/5224671-linear-integration-guide"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#drata__linear"
    },
    {
      "pair": "drata__microsoft-teams",
      "tool_a": "drata",
      "tool_a_name": "Drata",
      "tool_b": "microsoft-teams",
      "tool_b_name": "Microsoft Teams",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "drata",
      "data_flows_to": "microsoft-teams",
      "mechanism": "Drata app for Microsoft Teams (notifications)",
      "what_syncs": [
        "Alerts for not ready controls",
        "Alerts for personnel with pending compliance actions"
      ],
      "plan_requirements": "The Drata app must be installed in Teams, which may need IT approval. Drata role of Admin, Workspace Manager, or DevOps Engineer.",
      "notes": "Notifications go to the channel identified by the team URL and cannot be sent to private channels. Drata does not read data from Teams.",
      "source_urls": [
        "https://help.drata.com/en/articles/6556025-microsoft-teams-integration-guide"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#drata__microsoft-teams"
    },
    {
      "pair": "drata__notion",
      "tool_a": "drata",
      "tool_a_name": "Drata",
      "tool_b": "notion",
      "tool_b_name": "Notion",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "notion",
      "data_flows_to": "drata",
      "mechanism": "Drata Notion connection (policy sync)",
      "what_syncs": [
        "Notion policy pages imported into Drata",
        "Policies routed for approval and acknowledgement"
      ],
      "plan_requirements": "A Notion Enterprise plan and administrative access to the Notion workspace holding the policy pages. Drata role of Admin, Workspace Manager, or DevOps Engineer.",
      "notes": "Drata can access every page in the connected Notion account because page selection is not supported. Attachments, personal or private pages, and pages with database blocks do not sync.",
      "source_urls": [
        "https://help.drata.com/en/articles/9294590-notion-integration-guide"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#drata__notion"
    },
    {
      "pair": "drata__okta",
      "tool_a": "drata",
      "tool_a_name": "Drata",
      "tool_b": "okta",
      "tool_b_name": "Okta",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "okta",
      "data_flows_to": "drata",
      "mechanism": "Drata Okta connection (User Access Review); Drata Okta identity provider connection",
      "what_syncs": [
        "Okta users and groups",
        "Role assignments and role metadata",
        "Suspended and deactivated account status",
        "Identity metadata and logs"
      ],
      "plan_requirements": "An existing Okta identity provider connection in Drata is a prerequisite for the User Access Review connection. An Okta Super Admin must create a custom read-only admin role and resource set, assigned to a dedicated service account that generates the API token.",
      "notes": "Access is read-only. Apps that Okta does not fully provision, and access granted directly inside an app, may not be visible in reviews. Without an HRIS, Drata takes hire dates from Okta profile creation (overridable with a drataStartDate attribute) and separation dates from Okta deactivation. Nested groups do not sync.",
      "source_urls": [
        "https://help.drata.com/en/articles/8542832-okta-integration-guide-user-access-review",
        "https://help.drata.com/en/articles/5608136-okta-connection-for-identity-management",
        "https://help.drata.com/en/articles/13344234-how-drata-uses-hris-data"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#drata__okta"
    },
    {
      "pair": "drata__rippling",
      "tool_a": "drata",
      "tool_a_name": "Drata",
      "tool_b": "rippling",
      "tool_b_name": "Rippling",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "rippling",
      "data_flows_to": "drata",
      "mechanism": "Drata Rippling connection (HRIS, MDM, UAR)",
      "what_syncs": [
        "Employee hire dates",
        "Employee termination dates",
        "Employment status",
        "Device configuration data when Rippling MDM is enabled"
      ],
      "plan_requirements": "The organization must have purchased the Rippling App Management Package, and the connecting user needs Admin access in Rippling. In Drata, the Admin, Workspace Manager, or DevOps Engineer role is required.",
      "notes": "Rippling must be connected as an HRIS before MDM can be enabled. Rippling does not expose automatic security patch settings, so that evidence has to be uploaded manually for each device.",
      "source_urls": [
        "https://help.drata.com/en/articles/5014534-rippling-integration-guide-hris-mdm-uar"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#drata__rippling"
    },
    {
      "pair": "drata__salesforce",
      "tool_a": "drata",
      "tool_a_name": "Drata",
      "tool_b": "salesforce",
      "tool_b_name": "Salesforce",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "salesforce",
      "data_flows_to": "drata",
      "mechanism": "Drata Salesforce connection (User Access Review and CRM connection types)",
      "what_syncs": [
        "Salesforce users with ID, name, username and email into Drata user access reviews",
        "Group memberships, role assignments, permission identifiers and an admin flag",
        "Per-user MFA status, when the connecting profile has the Manage Multi-Factor Authentication in API permission",
        "UserType, used to identify service accounts",
        "Leads and opportunities queried on demand for Trust Center document access and NDA checks (CRM connection)"
      ],
      "plan_requirements": "User Access Review is included in Drata Enterprise and an add-on for Foundation and Advanced. The CRM connection requires Drata Trust Center Pro. Drata does not state a required Salesforce edition. Pricing is quote-based.",
      "notes": "Both connection types are read-only; Drata writes nothing to Salesforce. MFA status only shows if MFA is enabled in Salesforce. 'Unable to create a connection' usually means the org restricts the Drata connected app by IP; relax IP restrictions in App Manager. Drata's Sept 2025 blog announces Trust Center activity sync to Salesforce, which its help center associates with the SafeBase Trust Center rather than Trust Center Pro.",
      "source_urls": [
        "https://help.drata.com/en/articles/9923104-salesforce-connection",
        "https://help.drata.com/en/articles/9796974-salesforce-streamline-your-documentation-access-request",
        "https://drata.com/pricing"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#drata__salesforce"
    },
    {
      "pair": "drata__slack",
      "tool_a": "drata",
      "tool_a_name": "Drata",
      "tool_b": "slack",
      "tool_b_name": "Slack",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Drata Slack connection (Communication and User Access Review)",
      "what_syncs": [
        "Compliance notifications posted to Slack channels",
        "Alerts for not ready controls and pending tasks",
        "Channel identifiers read to target posts",
        "Slack users and roles read for access reviews"
      ],
      "plan_requirements": "Permission to install apps in the Slack workspace (owner approval may be needed). In Drata, the Admin, Workspace Manager, or DevOps Engineer role is required.",
      "notes": "Drata connects to a single Slack workspace and does not read messages or channel history. User Access Review is optional and can only be enabled after the Communication connection is in place.",
      "source_urls": [
        "https://help.drata.com/en/articles/6425963-slack-integration-guide-communication-and-uar"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#drata__slack"
    },
    {
      "pair": "drata__snowflake",
      "tool_a": "drata",
      "tool_a_name": "Drata",
      "tool_b": "snowflake",
      "tool_b_name": "Snowflake",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "snowflake",
      "data_flows_to": "drata",
      "mechanism": "Drata Snowflake connection (User Access Review)",
      "what_syncs": [
        "List of users with Snowflake access",
        "User access data for access reviews"
      ],
      "plan_requirements": "A Snowflake ACCOUNTADMIN for setup, plus a dedicated service user whose role has imported privileges on the SNOWFLAKE database and usage on a warehouse. Drata role of Admin, Workspace Manager, or DevOps Engineer.",
      "notes": "Scoped to user access reviews only. The service user should use key-pair or SSO authentication because Snowflake is retiring password-only sign-in for service users.",
      "source_urls": [
        "https://help.drata.com/en/articles/8987822-snowflake-integration-guide"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#drata__snowflake"
    },
    {
      "pair": "ebay__shopify",
      "tool_a": "ebay",
      "tool_a_name": "eBay",
      "tool_b": "shopify",
      "tool_b_name": "Shopify",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Shopify Marketplace Connect",
      "what_syncs": [
        "Product listings published to eBay",
        "Product and order changes synced to marketplaces",
        "Inventory sync",
        "Prices converted to marketplace local currency",
        "eBay orders imported into the Shopify admin to fulfill there (all orders, or only merchant-fulfilled ones)",
        "Tracking sent back to the marketplace"
      ],
      "plan_requirements": "Free to install. First 50 marketplace-synced orders per month are free, then a 1% fee per additional synced order, capped at $99 per month.",
      "notes": "Built by Shopify. Product, price and inventory changes go from Shopify to the marketplace, and marketplace orders are imported into Shopify. Orders that miss the automatic import can be imported by hand.",
      "source_urls": [
        "https://apps.shopify.com/marketplace-connect",
        "https://help.shopify.com/en/manual/online-sales-channels/marketplace-connect",
        "https://help.shopify.com/en/manual/online-sales-channels/marketplace-connect/manage-orders/import"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#ebay__shopify"
    },
    {
      "pair": "github__vanta",
      "tool_a": "github",
      "tool_a_name": "GitHub",
      "tool_b": "vanta",
      "tool_b_name": "Vanta",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Vanta GitHub integration",
      "what_syncs": [
        "GitHub accounts and invitations",
        "Repositories and pull request evidence",
        "Organization settings",
        "Vulnerabilities detected by GitHub",
        "GitHub Issues tracked as security tasks",
        "Tickets created in GitHub Issues from Vanta"
      ],
      "plan_requirements": "",
      "notes": "Most of the integration is read-only evidence collection. The one write described on the listing is creating tickets in GitHub Issues.",
      "source_urls": [
        "https://www.vanta.com/integrations/github"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#github__vanta"
    },
    {
      "pair": "gmail__hubspot",
      "tool_a": "gmail",
      "tool_a_name": "Gmail",
      "tool_b": "hubspot",
      "tool_b_name": "HubSpot",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "HubSpot connected inbox for Gmail",
      "what_syncs": [
        "Emails sent from HubSpot through Gmail",
        "Emails and replies logged in HubSpot",
        "Scheduled sends and drafts managed from HubSpot"
      ],
      "plan_requirements": "Available on all HubSpot products and plans. Users with a View-Only seat cannot connect an individual work email.",
      "notes": "Gmail accounts enrolled in Google's Advanced Protection Program are not supported. One email account cannot be both an individual work email and a team email.",
      "source_urls": [
        "https://knowledge.hubspot.com/connected-email/connect-your-inbox-to-hubspot"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#gmail__hubspot"
    },
    {
      "pair": "google-ads__hubspot",
      "tool_a": "google-ads",
      "tool_a_name": "Google Ads",
      "tool_b": "hubspot",
      "tool_b_name": "HubSpot",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "google-ads",
      "data_flows_to": "hubspot",
      "mechanism": "HubSpot ads tool Google Ads connection",
      "what_syncs": [
        "Existing Google Ads campaigns shown in HubSpot",
        "Campaign settings such as budget and bid strategy",
        "Campaign performance metrics"
      ],
      "plan_requirements": "Available on all HubSpot products and plans. The user needs Publish access to the HubSpot ads tools and Admin access to the individual Google Ads account.",
      "notes": "Only individual Google Ads accounts can be connected, not manager accounts.",
      "source_urls": [
        "https://knowledge.hubspot.com/ads/connect-your-google-ads-account-to-hubspot"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#google-ads__hubspot"
    },
    {
      "pair": "google-analytics-4__livestorm",
      "tool_a": "google-analytics-4",
      "tool_a_name": "Google Analytics 4",
      "tool_b": "livestorm",
      "tool_b_name": "Livestorm",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "livestorm",
      "data_flows_to": "google-analytics-4",
      "mechanism": "Livestorm Google Analytics integration (GA4 Measurement ID)",
      "what_syncs": [
        "GA4 tag on registration and company pages",
        "Registration event sent to Google Analytics",
        "Optional custom conversion event via custom code"
      ],
      "plan_requirements": "Available on all Livestorm plans; Livestorm admin or workspace owner.",
      "notes": "Only GA4 is supported, and registrants who decline Livestorm cookies are not tracked. It must be enabled on each event created before setup.",
      "source_urls": [
        "https://support.livestorm.co/article/57-connect-google-analytics-livestorm"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#google-analytics-4__livestorm"
    },
    {
      "pair": "google-analytics-4__shopify",
      "tool_a": "google-analytics-4",
      "tool_a_name": "Google Analytics 4",
      "tool_b": "shopify",
      "tool_b_name": "Shopify",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "shopify",
      "data_flows_to": "google-analytics-4",
      "mechanism": "Google & YouTube app for Shopify (GA4 tag)",
      "what_syncs": [
        "Ecommerce events tracked automatically after setup",
        "Product views",
        "Add-to-cart actions",
        "Completed purchases"
      ],
      "plan_requirements": "Requires a Google account, a GA4 property with a web data stream, and the Google & YouTube channel installed.",
      "notes": "Connecting Google Merchant Center is not needed for the GA4 tag setup. Google Analytics cannot track events while the online store is in private mode.",
      "source_urls": [
        "https://help.shopify.com/en/manual/reports-and-analytics/google-analytics/google-analytics-setup",
        "https://apps.shopify.com/google"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#google-analytics-4__shopify"
    },
    {
      "pair": "google-calendar__greenhouse",
      "tool_a": "google-calendar",
      "tool_a_name": "Google Calendar",
      "tool_b": "greenhouse",
      "tool_b_name": "Greenhouse",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Greenhouse Recruiting Google Calendar integration",
      "what_syncs": [
        "Interviewer availability read from Google Calendar",
        "Interview events created on calendars",
        "Interview events updated and deleted"
      ],
      "plan_requirements": "Greenhouse Core, Plus, or Pro subscription tiers; each user connects their own Google account.",
      "notes": "Each Greenhouse user links one Google Calendar account, and scheduling works only on calendars where the user can change events.",
      "source_urls": [
        "https://support.greenhouse.io/hc/en-us/articles/360021799232-Google-Calendar-integration"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#google-calendar__greenhouse"
    },
    {
      "pair": "google-calendar__hubspot",
      "tool_a": "google-calendar",
      "tool_a_name": "Google Calendar",
      "tool_b": "hubspot",
      "tool_b_name": "HubSpot",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "HubSpot calendar sync with Google Calendar",
      "what_syncs": [
        "HubSpot meetings added to Google Calendar",
        "Calendar events logged on contact timelines",
        "Calendar edits and deletions update HubSpot"
      ],
      "plan_requirements": "Available on all HubSpot products and plans.",
      "notes": "Only the primary calendar syncs, and events created before connecting are not synced. Deleting a meeting in HubSpot does not remove it from the calendar, and Google Calendar and Outlook Calendar cannot both be connected at once.",
      "source_urls": [
        "https://knowledge.hubspot.com/integrations/use-hubspots-integration-with-google-calendar-or-outlook-calendar"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#google-calendar__hubspot"
    },
    {
      "pair": "google-sheets__hubspot",
      "tool_a": "google-sheets",
      "tool_a_name": "Google Sheets",
      "tool_b": "hubspot",
      "tool_b_name": "HubSpot",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "hubspot",
      "data_flows_to": "google-sheets",
      "mechanism": "HubSpot workflow Google Sheets actions",
      "what_syncs": [
        "HubSpot record data added or updated as Google Sheets rows from workflows"
      ],
      "plan_requirements": "HubSpot Professional or Enterprise (workflows).",
      "notes": "Each action writes up to 20 cells per row and inserts rows rather than overwriting. A timeout can create a duplicate row. HubSpot recommends one workflow per sheet.",
      "source_urls": [
        "https://knowledge.hubspot.com/workflows/add-data-to-google-sheets-with-workflows"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#google-sheets__hubspot"
    },
    {
      "pair": "google-sheets__salesforce",
      "tool_a": "google-sheets",
      "tool_a_name": "Google Sheets",
      "tool_b": "salesforce",
      "tool_b_name": "Salesforce",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Data connector for Salesforce (Google Sheets add-on)",
      "what_syncs": [
        "Salesforce reports and SOQL query results imported into Sheets with manual or scheduled refresh",
        "Edits pushed from Sheets back to Salesforce records"
      ],
      "plan_requirements": "Free Google Sheets add-on; Salesforce account with API access.",
      "notes": "The add-on can delete highlighted records from Salesforce, so models should read from a separate tab.",
      "source_urls": [
        "https://support.google.com/docs/answer/9073952"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#google-sheets__salesforce"
    },
    {
      "pair": "greenhouse__rippling",
      "tool_a": "greenhouse",
      "tool_a_name": "Greenhouse",
      "tool_b": "rippling",
      "tool_b_name": "Rippling",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Greenhouse app in Rippling (Harvest API key)",
      "what_syncs": [
        "Candidate name, email, phone, Rejected At, and EEOC race/ethnicity and gender from Greenhouse into Rippling",
        "Offer and job data: job title, start date, salary, signing bonus, currency, work location and department",
        "Employment type from the employment_type custom field, when the value matches a type Rippling knows",
        "Referred By from the application's credited_to user, when that user is synced in Rippling",
        "Greenhouse user accounts provisioned and suspended from Rippling, plus SSO into Greenhouse"
      ],
      "plan_requirements": "Not stated in Greenhouse's integration doc.",
      "notes": "Hire data moves Greenhouse to Rippling; user account provisioning moves Rippling to Greenhouse. The import is manual: during Rippling onboarding choose Import from my ATS, then Greenhouse. The Harvest key needs read access to applications, candidates, offers, jobs and related endpoints, plus write access to Users.",
      "source_urls": [
        "https://support.greenhouse.io/hc/en-us/articles/360023220871-Rippling-integration"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#greenhouse__rippling"
    },
    {
      "pair": "greenhouse__slack",
      "tool_a": "greenhouse",
      "tool_a_name": "Greenhouse",
      "tool_b": "slack",
      "tool_b_name": "Slack",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Greenhouse Recruiting Slack integration",
      "what_syncs": [
        "New applicant and referral notifications",
        "Scorecard notifications and reminders",
        "Approval requests and offer approval notices",
        "@mention notifications",
        "Job and offer approvals submitted from Slack"
      ],
      "plan_requirements": "Greenhouse Core, Plus, or Pro subscription tiers; Basic user permission and above.",
      "notes": "Only one Slack channel can be selected for notifications. Posting to a shared channel can expose approval or candidate status to people without Greenhouse access.",
      "source_urls": [
        "https://support.greenhouse.io/hc/en-us/articles/207344866-Slack-integration"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#greenhouse__slack"
    },
    {
      "pair": "greenhouse__zoom",
      "tool_a": "greenhouse",
      "tool_a_name": "Greenhouse",
      "tool_b": "zoom",
      "tool_b_name": "Zoom",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Greenhouse Recruiting Zoom integration",
      "what_syncs": [
        "Interview host, start time, and duration to Zoom",
        "Zoom meeting link added to interviewer invite",
        "Link included in candidate confirmation email"
      ],
      "plan_requirements": "Greenhouse Core, Plus, or Pro subscription tiers; Job Admin and above; setup by a Zoom Admin account, with Greenhouse approved in the organization's Zoom App Marketplace.",
      "notes": "The meeting host cannot be changed after scheduling without deleting and rescheduling the interview. Canceling or deleting an interview does not remove the meeting from the Zoom account.",
      "source_urls": [
        "https://support.greenhouse.io/hc/en-us/articles/360042222612-Zoom-integration"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#greenhouse__zoom"
    },
    {
      "pair": "hubspot__intercom",
      "tool_a": "hubspot",
      "tool_a_name": "HubSpot",
      "tool_b": "intercom",
      "tool_b_name": "Intercom",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Intercom data sync app by HubSpot",
      "what_syncs": [
        "Intercom leads with HubSpot contacts",
        "Intercom users with HubSpot contacts",
        "Companies"
      ],
      "plan_requirements": "An Intercom subscription is required. Custom field mappings need a Data Hub Starter or Professional plan.",
      "notes": "Built by HubSpot. Tickets are not synced.",
      "source_urls": [
        "https://ecosystem.hubspot.com/marketplace/apps/intercom-data-sync"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#hubspot__intercom"
    },
    {
      "pair": "hubspot__jira",
      "tool_a": "hubspot",
      "tool_a_name": "HubSpot",
      "tool_b": "jira",
      "tool_b_name": "Jira",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "HubSpot Jira integration",
      "what_syncs": [
        "HubSpot tickets linked to Jira issues (issues also shown on contacts and companies)",
        "Comments in both directions",
        "Jira status, priority and assignee shown read-only on the ticket"
      ],
      "plan_requirements": "Free app on all HubSpot plans; workflows and reports on Jira properties need Professional or Enterprise. Jira Cloud only.",
      "notes": "Deals are not supported. Attachments on HubSpot notes do not sync. Legacy app property updates can take 1 to 24 hours.",
      "source_urls": [
        "https://knowledge.hubspot.com/integrations/install-and-use-hubspots-integration-with-jira"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#hubspot__jira"
    },
    {
      "pair": "hubspot__linkedin",
      "tool_a": "hubspot",
      "tool_a_name": "HubSpot",
      "tool_b": "linkedin",
      "tool_b_name": "LinkedIn",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "linkedin",
      "data_flows_to": "hubspot",
      "mechanism": "HubSpot ads tool LinkedIn Ads connection",
      "what_syncs": [
        "LinkedIn ad campaigns shown in HubSpot",
        "Campaign settings such as budget and creative",
        "Performance metrics such as impressions and clicks",
        "Leads from selected LinkedIn Ads accounts"
      ],
      "plan_requirements": "Available on all HubSpot products and plans. The user needs Publish access to the HubSpot ads tool and must be an Account Manager in the LinkedIn Ads account.",
      "notes": "Reporting covers only the most recent year of account data. LinkedIn Ads accounts that are on hold cannot be connected.",
      "source_urls": [
        "https://knowledge.hubspot.com/ads/connect-your-linkedin-ads-account-to-hubspot"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#hubspot__linkedin"
    },
    {
      "pair": "hubspot__livestorm",
      "tool_a": "hubspot",
      "tool_a_name": "HubSpot",
      "tool_b": "livestorm",
      "tool_b_name": "Livestorm",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Livestorm HubSpot integration",
      "what_syncs": [
        "Timeline events for registration and attendance",
        "No-show and replay view timeline events",
        "Marketing Events created per new session",
        "Contacts created for unknown registrants",
        "Companies created for unknown companies",
        "HubSpot form submissions register people in Livestorm"
      ],
      "plan_requirements": "Available on all Livestorm plans; Livestorm admin or workspace owner; a HubSpot Super Admin or user with App Marketplace Access must grant the conditionally required data permissions.",
      "notes": "Most data moves from Livestorm into HubSpot; the reverse direction is limited to registering people through HubSpot forms. The sync is not retroactive, new deals are no longer created, and existing events must be enabled one by one.",
      "source_urls": [
        "https://support.livestorm.co/article/setup-hubspot-integration"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#hubspot__livestorm"
    },
    {
      "pair": "hubspot__looker",
      "tool_a": "hubspot",
      "tool_a_name": "HubSpot",
      "tool_b": "looker",
      "tool_b_name": "Looker",
      "status": "no_native",
      "direction": "a_to_b",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "None; Looker connects only to SQL databases and warehouses",
      "what_syncs": [],
      "plan_requirements": "",
      "notes": "HubSpot data has to be loaded into a supported warehouse before Looker can query it.",
      "source_urls": [
        "https://docs.cloud.google.com/looker/docs/dialects"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#hubspot__looker"
    },
    {
      "pair": "hubspot__mailchimp",
      "tool_a": "hubspot",
      "tool_a_name": "HubSpot",
      "tool_b": "mailchimp",
      "tool_b_name": "Mailchimp",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Mailchimp data sync app by HubSpot",
      "what_syncs": [
        "Contacts, one-way or two-way"
      ],
      "plan_requirements": "HubSpot Data Hub Starter or higher. A Mailchimp subscription is required.",
      "notes": "Only contacts sync. Mailchimp groups, tags and email opens and clicks are not synced.",
      "source_urls": [
        "https://ecosystem.hubspot.com/marketplace/apps/mailchimp-data-sync"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#hubspot__mailchimp"
    },
    {
      "pair": "hubspot__microsoft-outlook",
      "tool_a": "hubspot",
      "tool_a_name": "HubSpot",
      "tool_b": "microsoft-outlook",
      "tool_b_name": "Microsoft Outlook",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "HubSpot connected inbox for Outlook; HubSpot calendar sync with Outlook Calendar",
      "what_syncs": [
        "One-to-one and sequence emails sent through Outlook",
        "Emails and replies logged in HubSpot",
        "HubSpot meetings added to the Outlook calendar",
        "Outlook calendar events logged on contact timelines"
      ],
      "plan_requirements": "Available on all HubSpot products and plans. Users with a View-Only seat cannot connect an individual work email.",
      "notes": "Microsoft 365 shared mailboxes are not supported for the inbox connection. Calendar sync covers only the default calendar, and Outlook events with bodies over 65,536 characters do not sync.",
      "source_urls": [
        "https://knowledge.hubspot.com/connected-email/connect-your-inbox-to-hubspot",
        "https://knowledge.hubspot.com/integrations/use-hubspots-integration-with-google-calendar-or-outlook-calendar"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#hubspot__microsoft-outlook"
    },
    {
      "pair": "hubspot__microsoft-teams",
      "tool_a": "hubspot",
      "tool_a_name": "HubSpot",
      "tool_b": "microsoft-teams",
      "tool_b_name": "Microsoft Teams",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "HubSpot app for Microsoft Teams",
      "what_syncs": [
        "HubSpot notifications sent to Teams",
        "Workflow messages posted to Teams channels",
        "Teams meeting links added to HubSpot meetings",
        "Tasks and tickets created from Teams",
        "Meeting recordings and transcripts synced to HubSpot",
        "Teams Phone call details logged to records",
        "Webinar attendance synced to HubSpot"
      ],
      "plan_requirements": "Available on all HubSpot products and plans. Help desk ticket sync to Teams needs Service Hub Professional or Enterprise. Needs a Microsoft work or school account; the admin-level install needs a Microsoft Global Admin.",
      "notes": "A user-level install only covers notifications, task and ticket creation and meeting links; recordings, transcripts, call logging and webinar sync need the admin-level install. Only one Teams instance can be connected per HubSpot account.",
      "source_urls": [
        "https://knowledge.hubspot.com/integrations/connect-hubspot-and-microsoft-teams"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#hubspot__microsoft-teams"
    },
    {
      "pair": "hubspot__netsuite",
      "tool_a": "hubspot",
      "tool_a_name": "HubSpot",
      "tool_b": "netsuite",
      "tool_b_name": "NetSuite",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "HubSpot NetSuite integration (HubSpot Sync Bundle in NetSuite)",
      "what_syncs": [
        "Contacts with NetSuite contacts and individuals",
        "Companies",
        "Deals with NetSuite opportunities",
        "Invoices",
        "Orders with NetSuite sales orders",
        "Products with NetSuite item types",
        "Tickets with NetSuite support cases",
        "Activities with calls, events and tasks"
      ],
      "plan_requirements": "Available on all HubSpot products and plans. Custom field mappings need a Data Hub subscription.",
      "notes": "Each sync can be set up as one-way or two-way. A NetSuite production or sandbox environment can be connected.",
      "source_urls": [
        "https://knowledge.hubspot.com/integrations/use-hubspots-integration-with-netsuite"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#hubspot__netsuite"
    },
    {
      "pair": "hubspot__pandadoc",
      "tool_a": "hubspot",
      "tool_a_name": "HubSpot",
      "tool_b": "pandadoc",
      "tool_b_name": "PandaDoc",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "PandaDoc HubSpot CRM integration",
      "what_syncs": [
        "Documents created from HubSpot contacts, companies, deals and tickets",
        "Deal stage moved on a chosen document status",
        "Signed PDF attached to the deal",
        "Deal and company properties updated",
        "Line items and deal amount synced",
        "New contacts created for unknown recipients"
      ],
      "plan_requirements": "PandaDoc Business or Enterprise. On Business, write-back sync rules need the External automations add-on ($39/month per account); Enterprise includes it. HubSpot tier not stated.",
      "notes": "Tickets support document creation but not sync rules.",
      "source_urls": [
        "https://support.pandadoc.com/en/articles/9714877-hubspot-crm-new-experience",
        "https://ecosystem.hubspot.com/marketplace/listing/pandadoc"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#hubspot__pandadoc"
    },
    {
      "pair": "hubspot__pipedrive",
      "tool_a": "hubspot",
      "tool_a_name": "HubSpot",
      "tool_b": "pipedrive",
      "tool_b_name": "Pipedrive",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Pipedrive data sync app by HubSpot",
      "what_syncs": [
        "Pipedrive people with HubSpot contacts",
        "Deals",
        "Pipedrive organizations with HubSpot companies",
        "Products",
        "Pipedrive activities with HubSpot engagements"
      ],
      "plan_requirements": "Pipedrive Essential, Advanced, Professional or Enterprise. Activity sync and custom field mappings need Data Hub Starter or higher.",
      "notes": "Built by HubSpot. Each sync can be set up as one-way or two-way; the listing does not give a fixed direction per object.",
      "source_urls": [
        "https://ecosystem.hubspot.com/marketplace/apps/pipedrive"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#hubspot__pipedrive"
    },
    {
      "pair": "hubspot__qlik",
      "tool_a": "hubspot",
      "tool_a_name": "HubSpot",
      "tool_b": "qlik",
      "tool_b_name": "Qlik",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Qlik Automate HubSpot connector",
      "what_syncs": [
        "HubSpot contacts, companies, deals, products, tickets and line items, read and written by Qlik Automate automations"
      ],
      "plan_requirements": "Qlik Cloud with Qlik Automate.",
      "notes": "This is an automation connector; a dedicated Qlik Cloud Analytics HubSpot data connector was not found.",
      "source_urls": [
        "https://community.qlik.com/t5/Official-Support-Articles/How-to-use-Hubspot-with-Qlik-Application-Automation/ta-p/1822717"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#hubspot__qlik"
    },
    {
      "pair": "hubspot__quickbooks",
      "tool_a": "hubspot",
      "tool_a_name": "HubSpot",
      "tool_b": "quickbooks",
      "tool_b_name": "QuickBooks",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "HubSpot QuickBooks Online integration",
      "what_syncs": [
        "Contacts with QuickBooks customers, two-way",
        "Products with products and services, two-way",
        "Invoices, two-way",
        "Credit memos, two-way or one-way",
        "Payments"
      ],
      "plan_requirements": "Available on all HubSpot products and plans; some features need additional subscriptions.",
      "notes": "Invoice sync is not usable with non-US QuickBooks Online accounts because HubSpot invoices cannot be created with tax. Only payments created after connecting sync, and QuickBooks sandbox accounts cannot be connected.",
      "source_urls": [
        "https://knowledge.hubspot.com/integrations/connect-hubspot-and-quickbooks-online"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#hubspot__quickbooks"
    },
    {
      "pair": "hubspot__salesforce",
      "tool_a": "hubspot",
      "tool_a_name": "HubSpot",
      "tool_b": "salesforce",
      "tool_b_name": "Salesforce",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "HubSpot-Salesforce connector",
      "what_syncs": [
        "HubSpot contacts with Salesforce leads and contacts",
        "HubSpot companies with Salesforce accounts",
        "HubSpot deals with Salesforce opportunities",
        "Tasks and activities (timeline events go from HubSpot to Salesforce only)",
        "Campaigns",
        "Custom objects on HubSpot Enterprise"
      ],
      "plan_requirements": "HubSpot Professional or Enterprise on any hub (Free and Starter cannot install it); custom object sync needs Enterprise. Salesforce needs an edition with API access or Professional Edition; Group Edition is not supported.",
      "notes": "Sync rule is chosen per field: two-way, prefer Salesforce, always Salesforce or always HubSpot. Records match by email. HubSpot checks for changes about every 15 minutes, and a contact sync can use up to 4 Salesforce API calls.",
      "source_urls": [
        "https://knowledge.hubspot.com/salesforce/install-the-hubspot-salesforce-integration",
        "https://knowledge.hubspot.com/salesforce/set-up-and-use-salesforce-custom-object-sync",
        "https://knowledge.hubspot.com/salesforce/salesforce-integration-sync-triggers"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#hubspot__salesforce"
    },
    {
      "pair": "hubspot__shopify",
      "tool_a": "hubspot",
      "tool_a_name": "HubSpot",
      "tool_b": "shopify",
      "tool_b_name": "Shopify",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Shopify data sync app by HubSpot",
      "what_syncs": [
        "Contacts and Shopify customers, two-way",
        "Companies, two-way",
        "Products, two-way",
        "Orders, Shopify to HubSpot only",
        "Abandoned checkouts as carts, Shopify to HubSpot only"
      ],
      "plan_requirements": "Custom field mappings need at least Data Hub Starter. Company sync needs Shopify Plus. Installing needs Super Admin or App Marketplace permissions in HubSpot.",
      "notes": "Orders synced from Shopify cannot be edited in HubSpot. Order sync does not detect or merge duplicate records.",
      "source_urls": [
        "https://knowledge.hubspot.com/integrations/connect-hubspot-and-shopify-via-data-sync"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#hubspot__shopify"
    },
    {
      "pair": "hubspot__slack",
      "tool_a": "hubspot",
      "tool_a_name": "HubSpot",
      "tool_b": "slack",
      "tool_b_name": "Slack",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "HubSpot app for Slack",
      "what_syncs": [
        "HubSpot notifications sent to Slack",
        "Workflow notifications posted to Slack channels",
        "Tasks, tickets and notes created from Slack messages",
        "HubSpot records shared into Slack channels",
        "Help desk tickets synced to a Slack channel"
      ],
      "plan_requirements": "Available on all HubSpot products and plans. Installing needs HubSpot Super Admin or App Marketplace permissions and a Slack workspace administrator. Workflow notifications need a Professional or Enterprise subscription.",
      "notes": "Private and Slack Connect channels need the HubSpot app added manually before they receive notifications. A ticket created from Slack supports up to 10 fields.",
      "source_urls": [
        "https://knowledge.hubspot.com/integrations/how-do-i-use-the-slack-integration",
        "https://knowledge.hubspot.com/integrations/manage-your-records-in-slack",
        "https://knowledge.hubspot.com/integrations/manage-your-notifications-in-slack"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#hubspot__slack"
    },
    {
      "pair": "hubspot__snowflake",
      "tool_a": "hubspot",
      "tool_a_name": "HubSpot",
      "tool_b": "snowflake",
      "tool_b_name": "Snowflake",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "hubspot",
      "data_flows_to": "snowflake",
      "mechanism": "HubSpot Snowflake Data Share",
      "what_syncs": [
        "HubSpot data shared into a Snowflake account",
        "Data queryable with SQL in Snowflake"
      ],
      "plan_requirements": "HubSpot Data Hub Enterprise. Installing needs Super Admin or App Marketplace permissions. An active Snowflake account is required.",
      "notes": "The customer pays all Snowflake costs for accessing the share, and HubSpot accounts with HIPAA turned on need a Snowflake Business Critical account. This entry covers the Data Share only.",
      "source_urls": [
        "https://knowledge.hubspot.com/integrations/connect-snowflake-data-share"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#hubspot__snowflake"
    },
    {
      "pair": "hubspot__stripe",
      "tool_a": "hubspot",
      "tool_a_name": "HubSpot",
      "tool_b": "stripe",
      "tool_b_name": "Stripe",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Stripe Data Sync app (built by HubSpot) and Stripe as HubSpot payment processor",
      "what_syncs": [
        "Stripe customers to HubSpot contacts",
        "Invoices, products and payment transactions",
        "Subscriptions on HubSpot Enterprise"
      ],
      "plan_requirements": "Free app on any HubSpot plan; subscription sync needs Enterprise and custom mapping needs Data Hub. Connecting Stripe as payment processor carries a 0.75% HubSpot fee.",
      "notes": "HubSpot Payments (US, UK, Canada) cannot be used alongside your own Stripe processor connection.",
      "source_urls": [
        "https://ecosystem.hubspot.com/marketplace/listing/stripe-data-sync",
        "https://knowledge.hubspot.com/payment-processing/connect-your-stripe-account-as-a-payment-processor-in-hubspot"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#hubspot__stripe"
    },
    {
      "pair": "hubspot__tableau",
      "tool_a": "hubspot",
      "tool_a_name": "HubSpot",
      "tool_b": "tableau",
      "tool_b_name": "Tableau",
      "status": "no_native",
      "direction": "a_to_b",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "None built in; third-party Tableau connector by Datawarehouse.io on the HubSpot App Marketplace",
      "what_syncs": [],
      "plan_requirements": "",
      "notes": "Tableau's connector list has no HubSpot connector. Data reaches Tableau through a third-party connector or a database populated by other tools.",
      "source_urls": [
        "https://help.tableau.com/current/pro/desktop/en-us/basicconnectoverview.htm"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#hubspot__tableau"
    },
    {
      "pair": "hubspot__vanta",
      "tool_a": "hubspot",
      "tool_a_name": "HubSpot",
      "tool_b": "vanta",
      "tool_b_name": "Vanta",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Vanta Trust Center HubSpot integration",
      "what_syncs": [
        "HubSpot records read to auto-approve Trust Center access",
        "HubSpot records read to decide NDA requirement",
        "Trust Center viewer activity pushed as HubSpot tasks",
        "Trust Center viewer activity pushed as HubSpot notes"
      ],
      "plan_requirements": "Covers advanced Trust Center features, which Vanta says may require an upgrade or add-on. The connection is set up with either read-only or write access.",
      "notes": "Read-only access is enough for access automation. Write access is needed for Vanta to push viewer activity to HubSpot, and each activity type is set to create either a task or a note.",
      "source_urls": [
        "https://help.vanta.com/en/articles/11345445-connecting-trust-center-hubspot"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#hubspot__vanta"
    },
    {
      "pair": "hubspot__xero",
      "tool_a": "hubspot",
      "tool_a_name": "HubSpot",
      "tool_b": "xero",
      "tool_b_name": "Xero",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Xero data sync app by HubSpot",
      "what_syncs": [
        "Contacts, one-way or two-way",
        "Items and products, one-way or two-way",
        "Invoices, Xero to HubSpot or two-way",
        "Invoice payments, Xero to HubSpot or two-way"
      ],
      "plan_requirements": "Available on all HubSpot products and plans. Custom field mappings need at least Data Hub Starter. Connecting needs Super Admin or App Marketplace permissions.",
      "notes": "Invoices created in HubSpot must be edited in HubSpot or the sync fails. Six currencies are supported, and only payments created after connecting sync.",
      "source_urls": [
        "https://knowledge.hubspot.com/integrations/connect-hubspot-and-xero-data-sync"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#hubspot__xero"
    },
    {
      "pair": "hubspot__zendesk",
      "tool_a": "hubspot",
      "tool_a_name": "HubSpot",
      "tool_b": "zendesk",
      "tool_b_name": "Zendesk",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Zendesk data sync app by HubSpot",
      "what_syncs": [
        "Zendesk users with HubSpot contacts",
        "Zendesk organizations with HubSpot companies",
        "Zendesk tickets with HubSpot tickets, one-way"
      ],
      "plan_requirements": "Zendesk Suite Team, Suite Growth or Suite Professional. Custom field mappings need Data Hub Starter or higher.",
      "notes": "The listing describes the sync as two-way overall but says ticket sync is one-way, without naming the ticket direction. The app is built by HubSpot.",
      "source_urls": [
        "https://ecosystem.hubspot.com/marketplace/apps/zendesk-data-sync"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#hubspot__zendesk"
    },
    {
      "pair": "hubspot__zoho-crm",
      "tool_a": "hubspot",
      "tool_a_name": "HubSpot",
      "tool_b": "zoho-crm",
      "tool_b_name": "Zoho CRM",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Zoho CRM data sync app by HubSpot",
      "what_syncs": [
        "Zoho contacts and leads with HubSpot contacts",
        "Zoho accounts with HubSpot companies",
        "Deals",
        "Products",
        "Invoices",
        "Calls, meetings, notes and tasks"
      ],
      "plan_requirements": "A Zoho CRM subscription is required. Custom field mappings need Data Hub Starter or higher.",
      "notes": "Built by HubSpot. Each sync can be one-way or two-way. The listing is inconsistent on custom modules, so treat custom module sync as unconfirmed.",
      "source_urls": [
        "https://ecosystem.hubspot.com/marketplace/apps/zoho-crm-data-sync"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#hubspot__zoho-crm"
    },
    {
      "pair": "hubspot__zoom",
      "tool_a": "hubspot",
      "tool_a_name": "HubSpot",
      "tool_b": "zoom",
      "tool_b_name": "Zoom",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "HubSpot Zoom integration",
      "what_syncs": [
        "Webinar registrations and attendance to HubSpot",
        "Webinars synced as marketing events",
        "Zoom meetings logged on contact records",
        "Cloud recordings and transcripts on contact timelines",
        "New contacts created from participants",
        "Workflow adds contacts as Zoom webinar registrants"
      ],
      "plan_requirements": "Available on all HubSpot products and plans, with some features limited to certain subscriptions. Webinar features need the Zoom webinar add-on. The connecting user needs Zoom admin permissions.",
      "notes": "Participants are matched to contacts by email. Recordings and transcripts sync only when cloud recording and audio transcripts are turned on in Zoom.",
      "source_urls": [
        "https://knowledge.hubspot.com/integrations/use-hubspots-integration-with-zoom"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#hubspot__zoom"
    },
    {
      "pair": "intercom__jira",
      "tool_a": "intercom",
      "tool_a_name": "Intercom",
      "tool_b": "jira",
      "tool_b_name": "Jira",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Intercom Jira for Tickets app",
      "what_syncs": [
        "Jira issues created from Intercom tickets",
        "Ticket notes to Jira comments and Jira comments to internal notes",
        "Jira status changes update the ticket"
      ],
      "plan_requirements": "Jira Cloud only; Intercom base plan not stated.",
      "notes": "Works from tickets, not conversations.",
      "source_urls": [
        "https://www.intercom.com/help/en/articles/7918909-jira-for-tickets-app"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#intercom__jira"
    },
    {
      "pair": "intercom__salesforce",
      "tool_a": "intercom",
      "tool_a_name": "Intercom",
      "tool_b": "salesforce",
      "tool_b_name": "Salesforce",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Salesforce app by Intercom",
      "what_syncs": [
        "Lead and contact attributes synced per field",
        "New Salesforce leads created from Intercom",
        "Conversations logged as completed Salesforce tasks",
        "Salesforce cases created from Intercom conversations",
        "Salesforce accounts mapped to Intercom companies"
      ],
      "plan_requirements": "Intercom Advanced or Expert plan with full admin permissions; sandbox installs need Expert. Salesforce edition with API access such as Enterprise or Unlimited (Professional needs the API add-on). The connecting Salesforce user needs API Enabled, View All Data, and read/write on Leads, Contacts, Accounts, and Tasks.",
      "notes": "Sync direction is chosen per mapped attribute and changes can take up to 5 minutes. Tags, events, compound fields, and high-frequency attributes such as last seen cannot be mapped.",
      "source_urls": [
        "https://www.intercom.com/help/en/articles/4497943-install-salesforce-integration",
        "https://www.intercom.com/help/en/articles/1047665-salesforce-integration-troubleshooting-and-faqs"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#intercom__salesforce"
    },
    {
      "pair": "intercom__shopify",
      "tool_a": "intercom",
      "tool_a_name": "Intercom",
      "tool_b": "shopify",
      "tool_b_name": "Shopify",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Fin AI Agent & Intercom app for Shopify",
      "what_syncs": [
        "Order, shipping, and customer data into Intercom",
        "Shopify events for targeted messaging",
        "Refunds issued from the Intercom inbox",
        "Shipping information edited from Intercom",
        "Orders created from Intercom"
      ],
      "plan_requirements": "Intercom seat plans listed: Essential, Advanced, Expert. Fin AI Agent is charged per outcome.",
      "notes": "The app is developed by Intercom. Multiple Shopify stores can be connected to one Intercom workspace.",
      "source_urls": [
        "https://apps.shopify.com/intercom"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#intercom__shopify"
    },
    {
      "pair": "ironclad__salesforce",
      "tool_a": "ironclad",
      "tool_a_name": "Ironclad",
      "tool_b": "salesforce",
      "tool_b_name": "Salesforce",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Ironclad Managed Package for Salesforce",
      "what_syncs": [
        "Contract workflows launched from Salesforce records with pre-filled forms",
        "Workflow, approval and signature status synced to Salesforce",
        "Contract records and Opportunity field updates written to Salesforce"
      ],
      "plan_requirements": "Ironclad managed package from AppExchange; plan and price not published.",
      "notes": "",
      "source_urls": [
        "https://ironcladapp.com/product/integrations/salesforce"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#ironclad__salesforce"
    },
    {
      "pair": "jira__monday",
      "tool_a": "jira",
      "tool_a_name": "Jira",
      "tool_b": "monday",
      "tool_b_name": "Monday.com",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "monday.com Jira Cloud integration and Jira Cloud Two-way sync app",
      "what_syncs": [
        "Jira issues mapped to board items",
        "Mapped fields with sync direction set per field (two-way app, beta)"
      ],
      "plan_requirements": "Not stated on the help page.",
      "notes": "Comments do not sync. The Jira Data Center app checks for changes every 3 minutes.",
      "source_urls": [
        "https://support.monday.com/hc/en-us/articles/36033101677074-Jira-Cloud-Two-way-sync-app",
        "https://support.monday.com/hc/en-us/articles/7238716251538-The-Jira-Cloud-integration"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#jira__monday"
    },
    {
      "pair": "jira__slack",
      "tool_a": "jira",
      "tool_a_name": "Jira",
      "tool_b": "slack",
      "tool_b_name": "Slack",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Jira Cloud for Slack",
      "what_syncs": [
        "Issues created with /jira create or from a message action",
        "Issues transitioned, assigned and commented on from Slack",
        "Slack threads synced to issues as comments",
        "Issue notifications to channels and Jira Automation Slack messages"
      ],
      "plan_requirements": "No plan requirement stated.",
      "notes": "",
      "source_urls": [
        "https://support.atlassian.com/jira-software-cloud/docs/use-jira-cloud-for-slack/"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#jira__slack"
    },
    {
      "pair": "jira__vanta",
      "tool_a": "jira",
      "tool_a_name": "Jira",
      "tool_b": "vanta",
      "tool_b_name": "Vanta",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Vanta Jira integration",
      "what_syncs": [
        "Jira accounts read for access tracking",
        "Labeled Jira issues imported as security tasks",
        "Jira issues created from failing Vanta tests",
        "Issue resolution in Jira closes the Vanta task"
      ],
      "plan_requirements": "Task creation is optional and needs write access; the connecting Jira user needs the Create Issues permission. Vanta recommends a dedicated service account.",
      "notes": "Task sync is label based and labels are case sensitive, so only issues with a matching label are imported. A separate connection exists for Jira Data Center, where Epic and Sub-task types cannot be created from Vanta.",
      "source_urls": [
        "https://www.vanta.com/integrations/jira",
        "https://help.vanta.com/en/articles/14441707-jira-integration-guide"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#jira__vanta"
    },
    {
      "pair": "jira__zendesk",
      "tool_a": "jira",
      "tool_a_name": "Jira",
      "tool_b": "zendesk",
      "tool_b_name": "Zendesk",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Zendesk Support for Jira (built by Zendesk)",
      "what_syncs": [
        "Zendesk tickets linked to Jira issues, up to 200 per issue",
        "Ticket comments to Jira and Jira comments to tickets"
      ],
      "plan_requirements": "Zendesk Support Team or above (or Suite Team or above); free app.",
      "notes": "Ticket status updates need a post-function in the Jira workflow. Public Jira comments email the customer.",
      "source_urls": [
        "https://support.zendesk.com/hc/en-us/articles/4408827996058",
        "https://marketplace.atlassian.com/apps/1211941/zendesk-support-for-jira"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#jira__zendesk"
    },
    {
      "pair": "klaviyo__salesforce",
      "tool_a": "klaviyo",
      "tool_a_name": "Klaviyo",
      "tool_b": "salesforce",
      "tool_b_name": "Salesforce",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "salesforce",
      "data_flows_to": "klaviyo",
      "mechanism": "Klaviyo Salesforce CRM integration",
      "what_syncs": [
        "Leads and contacts synced as Klaviyo profiles",
        "Accounts, opportunities, and other objects optional",
        "Mapped Salesforce fields become profile properties",
        "Became Lead metric tracked for new leads"
      ],
      "plan_requirements": "Admin access to the Salesforce account. The Klaviyo Salesforce OAuth Connector package must be installed in the Salesforce org.",
      "notes": "Sync runs every hour and up to 6 Salesforce objects can be selected. Each object needs a mapped email field, and the article describes no writeback from Klaviyo to Salesforce.",
      "source_urls": [
        "https://help.klaviyo.com/hc/en-us/articles/115005081947"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#klaviyo__salesforce"
    },
    {
      "pair": "klaviyo__shopify",
      "tool_a": "klaviyo",
      "tool_a_name": "Klaviyo",
      "tool_b": "shopify",
      "tool_b_name": "Shopify",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Klaviyo Shopify integration",
      "what_syncs": [
        "Customer profiles and order data into Klaviyo",
        "Shopify email and SMS subscribers to Klaviyo lists",
        "Onsite events such as Viewed Product, Added to Cart",
        "Shopify Markets catalogs into Klaviyo",
        "Klaviyo profiles and contact info to Shopify",
        "Subscription status and email/SMS events to Shopify",
        "Selected Klaviyo custom properties to Shopify"
      ],
      "plan_requirements": "",
      "notes": "Contact info synced to Shopify does not overwrite existing Shopify values, while locale can. Shopify Markets sync can be enabled in only one Klaviyo account per store, and some onsite events need Shopify Network Intelligence and the Klaviyo app embed turned on.",
      "source_urls": [
        "https://help.klaviyo.com/hc/en-us/articles/115005080407"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#klaviyo__shopify"
    },
    {
      "pair": "klaviyo__stripe",
      "tool_a": "klaviyo",
      "tool_a_name": "Klaviyo",
      "tool_b": "stripe",
      "tool_b_name": "Stripe",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "stripe",
      "data_flows_to": "klaviyo",
      "mechanism": "Klaviyo Stripe integration",
      "what_syncs": [
        "Successfully Paid, Failed Payment, Refunded Payment and Issued Invoice metrics with invoice line items",
        "Profiles created by email",
        "Up to five years of history on connect"
      ],
      "plan_requirements": "Plan requirement not stated; Klaviyo free plan covers up to 250 profiles, Email plan from $20/month.",
      "notes": "No subscription created, updated or canceled events.",
      "source_urls": [
        "https://help.klaviyo.com/hc/en-us/articles/115005082267"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#klaviyo__stripe"
    },
    {
      "pair": "linear__slack",
      "tool_a": "linear",
      "tool_a_name": "Linear",
      "tool_b": "slack",
      "tool_b_name": "Slack",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Linear Slack integration",
      "what_syncs": [
        "Issues created from Slack messages or /linear",
        "Synced threads that mirror Linear comments and Slack replies",
        "Assignee changes and comments from Slack",
        "Team notifications for new issues, comments, status changes and project updates"
      ],
      "plan_requirements": "No plan stated for the core integration; connecting multiple Slack workspaces needs Enterprise and Asks needs Business or Enterprise.",
      "notes": "",
      "source_urls": [
        "https://linear.app/docs/slack"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#linear__slack"
    },
    {
      "pair": "livestorm__pipedrive",
      "tool_a": "livestorm",
      "tool_a_name": "Livestorm",
      "tool_b": "pipedrive",
      "tool_b_name": "Pipedrive",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "livestorm",
      "data_flows_to": "pipedrive",
      "mechanism": "Livestorm Pipedrive integration (API token)",
      "what_syncs": [
        "Registrants and attendees as Pipedrive contacts",
        "Contact fields through custom mapping",
        "Deals created at registration or attendance",
        "Registration and attendance activity records",
        "Replay views and questions asked activities"
      ],
      "plan_requirements": "Available on any Livestorm plan; Livestorm workspace owner or admin; the Pipedrive user needs the API Keys permission.",
      "notes": "It is switched on or off for the whole workspace and cannot be set per event. Mapped values overwrite existing Pipedrive values.",
      "source_urls": [
        "https://support.livestorm.co/article/connect-pipedrive-and-livestorm"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#livestorm__pipedrive"
    },
    {
      "pair": "livestorm__salesforce",
      "tool_a": "livestorm",
      "tool_a_name": "Livestorm",
      "tool_b": "salesforce",
      "tool_b_name": "Salesforce",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "livestorm",
      "data_flows_to": "salesforce",
      "mechanism": "Livestorm Salesforce integration",
      "what_syncs": [
        "Sessions created as Salesforce Campaigns",
        "Registrants added as Campaign Members",
        "New Leads or Contacts created by email match",
        "Attended or did not attend status",
        "Replay view status on a custom field",
        "Engagement data through field mapping"
      ],
      "plan_requirements": "Livestorm Enterprise plan as a paid add-on; Livestorm admin or workspace owner; Salesforce Sales Cloud user with a System Administrator profile or custom permission set plus the Marketing User checkbox.",
      "notes": "The sync is not retroactive and campaign linking is automatic, with one campaign per session. Salesforce Marketing Cloud is not supported, and registration forms must collect first name, last name, email, and company as mandatory fields.",
      "source_urls": [
        "https://support.livestorm.co/article/connect-livestorm-salesforce-new"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#livestorm__salesforce"
    },
    {
      "pair": "livestorm__slack",
      "tool_a": "livestorm",
      "tool_a_name": "Livestorm",
      "tool_b": "slack",
      "tool_b_name": "Slack",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "livestorm",
      "data_flows_to": "slack",
      "mechanism": "Livestorm Slack integration (Slack incoming webhook)",
      "what_syncs": [
        "New registrant profiles posted to a channel"
      ],
      "plan_requirements": "",
      "notes": "Setup uses a Slack incoming webhook URL pasted into Livestorm settings. The integration is off by default for events created before it was set up.",
      "source_urls": [
        "https://support.livestorm.co/article/55-connect-slack-livestorm"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#livestorm__slack"
    },
    {
      "pair": "looker-studio__salesforce",
      "tool_a": "looker-studio",
      "tool_a_name": "Looker Studio",
      "tool_b": "salesforce",
      "tool_b_name": "Salesforce",
      "status": "no_native",
      "direction": "b_to_a",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "None from Google; partner connectors such as Power My Analytics and Adzviser",
      "what_syncs": [],
      "plan_requirements": "",
      "notes": "Looker Studio was renamed Data Studio on April 16, 2026. Google describes Salesforce connectors as third-party; most are paid.",
      "source_urls": [
        "https://docs.cloud.google.com/data-studio/release-notes",
        "https://cloud.google.com/looker/docs/studio/about-connectors-data-sources-and-credentials"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#looker-studio__salesforce"
    },
    {
      "pair": "looker__salesforce",
      "tool_a": "looker",
      "tool_a_name": "Looker",
      "tool_b": "salesforce",
      "tool_b_name": "Salesforce",
      "status": "no_native",
      "direction": "b_to_a",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "None; Looker connects only to SQL databases and warehouses",
      "what_syncs": [],
      "plan_requirements": "",
      "notes": "Salesforce data has to be loaded into a supported warehouse before Looker can query it.",
      "source_urls": [
        "https://docs.cloud.google.com/looker/docs/dialects"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#looker__salesforce"
    },
    {
      "pair": "mailchimp__shopify",
      "tool_a": "mailchimp",
      "tool_a_name": "Mailchimp",
      "tool_b": "shopify",
      "tool_b_name": "Shopify",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Mailchimp for Shopify",
      "what_syncs": [
        "Shopify customers added to a Mailchimp audience",
        "Customer subscription status",
        "SMS subscribers, Shopify to Mailchimp only",
        "Customer events like product views and checkouts",
        "B2B company data as a merge tag",
        "Email and SMS activity back to Shopify",
        "New Mailchimp contacts as Shopify customers (optional)"
      ],
      "plan_requirements": "No Mailchimp plan tier stated. Syncing SMS subscribers requires an approved Mailchimp SMS Marketing program.",
      "notes": "Most fields update in near real time, but the discount code field syncs every few hours. Customer events shared by Shopify are limited when the store has Shopify GDPR or CCPA policies enabled.",
      "source_urls": [
        "https://mailchimp.com/help/mailchimp-shopify-syncing/"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#mailchimp__shopify"
    },
    {
      "pair": "monday__pandadoc",
      "tool_a": "monday",
      "tool_a_name": "Monday.com",
      "tool_b": "pandadoc",
      "tool_b_name": "PandaDoc",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "monday",
      "data_flows_to": "pandadoc",
      "mechanism": "PandaDoc app for monday.com",
      "what_syncs": [
        "monday.com item column values filled into PandaDoc document variables",
        "Document status displayed in the item widget"
      ],
      "plan_requirements": "PandaDoc Business or Enterprise; a monday.com admin installs the app.",
      "notes": "Writing status back to board columns is not documented. Line items, formula columns and the monday desktop app are not supported.",
      "source_urls": [
        "https://support.pandadoc.com/en/articles/9714891-monday-com"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#monday__pandadoc"
    },
    {
      "pair": "monday__salesforce",
      "tool_a": "monday",
      "tool_a_name": "Monday.com",
      "tool_b": "salesforce",
      "tool_b_name": "Salesforce",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "monday.com Salesforce integration and Salesforce Two-way sync app",
      "what_syncs": [
        "Salesforce records into monday.com boards",
        "Two-way field sync through the paid add-on app"
      ],
      "plan_requirements": "monday.com Enterprise plan; two-way sync is a paid add-on. Salesforce Enterprise or Unlimited.",
      "notes": "The two-way sync app polls for changes every 3 minutes.",
      "source_urls": [
        "https://support.monday.com/hc/en-us/articles/360009513540-Salesforce-Integration",
        "https://support.monday.com/hc/en-us/articles/31309659658642-Salesforce-Two-way-sync-app"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#monday__salesforce"
    },
    {
      "pair": "netsuite__salesforce",
      "tool_a": "netsuite",
      "tool_a_name": "NetSuite",
      "tool_b": "salesforce",
      "tool_b_name": "Salesforce",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "NetSuite Connector for Salesforce (Oracle SuiteApp on Oracle Integration Cloud)",
      "what_syncs": [
        "Subsidiaries",
        "NetSuite items with Salesforce products in both directions",
        "NetSuite customers with Salesforce accounts in both directions",
        "Contacts",
        "Closed-won opportunities to NetSuite sales orders",
        "Sales orders, fulfillments, invoices, payments and cash sales back to Salesforce"
      ],
      "plan_requirements": "NetSuite OneWorld account with at least one subsidiary; Salesforce edition with API access, an API-only integration user and an External Client App.",
      "notes": "Installed from the NetSuite side. Oracle's documentation does not say whether custom fields or custom records are supported. Third-party options with documented custom record support include Celigo and Breadwinner.",
      "source_urls": [
        "https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/article_4130552285.html",
        "https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/article_2155722791.html"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#netsuite__salesforce"
    },
    {
      "pair": "notion__slack",
      "tool_a": "notion",
      "tool_a_name": "Notion",
      "tool_b": "slack",
      "tool_b_name": "Slack",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Notion for Slack and Notion database automations",
      "what_syncs": [
        "Slack messages sent to a Notion database with /notion create, /notion task or Send to Notion",
        "Slack notifications from database automations when a page is added or a property changes",
        "Link previews for Notion pages shared in Slack"
      ],
      "plan_requirements": "Notion's docs conflict on whether the Slack notification automation needs Plus, Business or Enterprise or also works on Free.",
      "notes": "Send to Notion works on channel messages, not thread replies. Notion pages cannot be updated from Slack.",
      "source_urls": [
        "https://www.notion.com/help/slack",
        "https://www.notion.com/help/database-automations"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#notion__slack"
    },
    {
      "pair": "notion__vanta",
      "tool_a": "notion",
      "tool_a_name": "Notion",
      "tool_b": "vanta",
      "tool_b_name": "Vanta",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Vanta Notion integration",
      "what_syncs": [
        "Notion security tasks monitored in Vanta",
        "New Notion tasks created for failed tests",
        "Notion user access tracked for access reviews"
      ],
      "plan_requirements": "",
      "notes": "Built by Vanta. The listing gives no plan requirements or field-level detail.",
      "source_urls": [
        "https://www.vanta.com/integrations/notion"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#notion__vanta"
    },
    {
      "pair": "okta__salesforce",
      "tool_a": "okta",
      "tool_a_name": "Okta",
      "tool_b": "salesforce",
      "tool_b_name": "Salesforce",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Okta Salesforce provisioning integration",
      "what_syncs": [
        "New Okta users pushed to Salesforce",
        "Okta profile updates pushed to Salesforce",
        "Okta deactivation deactivates the Salesforce user",
        "Salesforce users imported into Okta",
        "Salesforce profile updates imported into Okta",
        "Salesforce user accounts reactivated"
      ],
      "plan_requirements": "",
      "notes": "The supported features page states no edition or license requirements. Create, update, and deactivate options must be turned on in the app's provisioning settings, otherwise provisioning fails.",
      "source_urls": [
        "https://help.okta.com/en-us/content/topics/provisioning/salesforce/sfdc-supported-features.htm"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#okta__salesforce"
    },
    {
      "pair": "okta__vanta",
      "tool_a": "okta",
      "tool_a_name": "Okta",
      "tool_b": "vanta",
      "tool_b_name": "Vanta",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "okta",
      "data_flows_to": "vanta",
      "mechanism": "Vanta Okta API integration (separate Okta SSO and SCIM apps)",
      "what_syncs": [
        "Users with status, activation, last login and MFA enrollment",
        "MFA factors and admin role assignments",
        "Groups and their members",
        "Applications and their assigned users",
        "Password and authentication policies"
      ],
      "plan_requirements": "An Okta Super Administrator connects it, and the Okta API Services app also needs the Super Administrator role plus six read-only scopes. OAuth with a private key is the default; an API token is the fallback.",
      "notes": "Read-only; provisioning into Vanta needs the separate SCIM app. Vanta treats the HRIS as the source of truth for employment status and uses Okta account status for offboarding tests. Each Vanta workspace needs its own Okta API app.",
      "source_urls": [
        "https://help.vanta.com/en/articles/15082003-okta-integration-guide",
        "https://www.vanta.com/integrations/okta"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#okta__vanta"
    },
    {
      "pair": "pandadoc__pipedrive",
      "tool_a": "pandadoc",
      "tool_a_name": "PandaDoc",
      "tool_b": "pipedrive",
      "tool_b_name": "Pipedrive",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "PandaDoc Pipedrive integration",
      "what_syncs": [
        "Documents created from Pipedrive deals, contacts and organizations",
        "Deal fields and document value written back",
        "Signed PDF saved to the deal's files",
        "Deal stage moved by document status and won/lost status set",
        "Products added, updated or removed"
      ],
      "plan_requirements": "PandaDoc Business or Enterprise.",
      "notes": "",
      "source_urls": [
        "https://support.pandadoc.com/en/articles/9714881-pipedrive"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#pandadoc__pipedrive"
    },
    {
      "pair": "pandadoc__salesforce",
      "tool_a": "pandadoc",
      "tool_a_name": "PandaDoc",
      "tool_b": "salesforce",
      "tool_b_name": "Salesforce",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "PandaDoc for Salesforce (two-way sync)",
      "what_syncs": [
        "Documents created from Opportunity, Account, Lead, Contact, standard Quote and custom objects",
        "Document status mapped to Opportunity stage per template",
        "Signed PDF saved to Salesforce Files and events logged in Notes & Attachments",
        "Opportunity Products updated from the document",
        "Document field values and system variables written to Salesforce fields"
      ],
      "plan_requirements": "PandaDoc Business or Enterprise on annual billing plus the paid Salesforce add-on (quote-only). Salesforce Enterprise or Unlimited, or Professional with API access.",
      "notes": "Professional without API access can create documents but nothing syncs back. Salesforce CPQ quotes need PandaDoc's separate CPQ package. Automatic creation on a stage change needs PandaDoc custom triggers (developer work).",
      "source_urls": [
        "https://support.pandadoc.com/en/articles/9714863-salesforce-2-way-sync",
        "https://www.pandadoc.com/pricing/"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#pandadoc__salesforce"
    },
    {
      "pair": "pandadoc__zoho-crm",
      "tool_a": "pandadoc",
      "tool_a_name": "PandaDoc",
      "tool_b": "zoho-crm",
      "tool_b_name": "Zoho CRM",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "PandaDoc extension for Zoho CRM",
      "what_syncs": [
        "Documents created from Zoho accounts, contacts, deals, leads and quotes",
        "Document status shown on the Zoho record",
        "Completed PDF attached to the record (up to 20 MB)"
      ],
      "plan_requirements": "PandaDoc Business or Enterprise; any paid Zoho CRM edition.",
      "notes": "Installed from the Zoho CRM marketplace. Deal stage changes need PandaDoc's Workato-based Zoho automations; deal amount does not sync natively.",
      "source_urls": [
        "https://support.pandadoc.com/en/articles/9714903-zoho-crm",
        "https://support.pandadoc.com/en/articles/9714999-zoho-automations"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#pandadoc__zoho-crm"
    },
    {
      "pair": "paypal__quickbooks",
      "tool_a": "paypal",
      "tool_a_name": "PayPal",
      "tool_b": "quickbooks",
      "tool_b_name": "QuickBooks",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "paypal",
      "data_flows_to": "quickbooks",
      "mechanism": "PayPal Connector by QuickBooks",
      "what_syncs": [
        "PayPal sales and expense transactions with tax and fees, as sales receipts or deposits"
      ],
      "plan_requirements": "QuickBooks Online; price and plan not stated by Intuit.",
      "notes": "Built by Intuit. Only balance-affecting transactions sync; multi-currency is not supported.",
      "source_urls": [
        "https://quickbooks.intuit.com/learn-support/en-us/help-article/account-management/connect-quickbooks-online-paypal/L4kRBkssE_US_en_US"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#paypal__quickbooks"
    },
    {
      "pair": "qlik__salesforce",
      "tool_a": "qlik",
      "tool_a_name": "Qlik",
      "tool_b": "salesforce",
      "tool_b_name": "Salesforce",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "salesforce",
      "data_flows_to": "qlik",
      "mechanism": "Qlik Cloud Salesforce connector",
      "what_syncs": [
        "Salesforce data loaded into Qlik Sense apps"
      ],
      "plan_requirements": "Qlik Cloud; Salesforce account with API access.",
      "notes": "Supports Salesforce API up to version 56. No separate install needed on Qlik Cloud.",
      "source_urls": [
        "https://help.qlik.com/en-US/cloud-services/Subsystems/Salesforce_Connector_help/Content/Connectors_Salesforce/Introduction/Salesforce-connector.htm"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#qlik__salesforce"
    },
    {
      "pair": "quickbooks__shopify",
      "tool_a": "quickbooks",
      "tool_a_name": "QuickBooks",
      "tool_b": "shopify",
      "tool_b_name": "Shopify",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "shopify",
      "data_flows_to": "quickbooks",
      "mechanism": "Shopify Connector by QuickBooks",
      "what_syncs": [
        "Orders as sales receipts (B2B orders as invoices)",
        "Refunds as separate transactions",
        "Payouts as deposits and fees as expenses",
        "Taxes"
      ],
      "plan_requirements": "QuickBooks Online; price and plan not stated by Intuit.",
      "notes": "Built by Intuit. Can backfill up to one year of orders.",
      "source_urls": [
        "https://quickbooks.intuit.com/learn-support/en-us/help-article/manage-integrations/connect-shopify-quickbooks-online/L1Xv7ZCFB_US_en_US"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#quickbooks__shopify"
    },
    {
      "pair": "quickbooks__stripe",
      "tool_a": "quickbooks",
      "tool_a_name": "QuickBooks",
      "tool_b": "stripe",
      "tool_b_name": "Stripe",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "stripe",
      "data_flows_to": "quickbooks",
      "mechanism": "Stripe Connector by QuickBooks",
      "what_syncs": [
        "Stripe sales, refunds, payouts, adjustments and disputes",
        "Stripe fees to a Stripe Fees expense account",
        "Customers matched"
      ],
      "plan_requirements": "QuickBooks Online; price and plan not stated by Intuit.",
      "notes": "Built by Intuit. Transactions usually appear within 2 hours.",
      "source_urls": [
        "https://quickbooks.intuit.com/learn-support/en-us/help-article/manage-integrations/connect-manage-stripe-transactions-quickbooks/L10TzOVcN_US_en_US"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#quickbooks__stripe"
    },
    {
      "pair": "rippling__salesforce",
      "tool_a": "rippling",
      "tool_a_name": "Rippling",
      "tool_b": "salesforce",
      "tool_b_name": "Salesforce",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "rippling",
      "data_flows_to": "salesforce",
      "mechanism": "Rippling Salesforce app (identity and app management)",
      "what_syncs": [
        "Salesforce users and licences created, changed and suspended from Rippling HR role and department rules"
      ],
      "plan_requirements": "Rippling IT; plan not verified.",
      "notes": "No sync from Salesforce back to Rippling is documented.",
      "source_urls": [
        "https://www.rippling.com/products/it/identity-access-management",
        "https://www.rippling.com/blog/automate-the-boring-parts-of-it-with-rippling"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#rippling__salesforce"
    },
    {
      "pair": "rippling__vanta",
      "tool_a": "rippling",
      "tool_a_name": "Rippling",
      "tool_b": "vanta",
      "tool_b_name": "Vanta",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "rippling",
      "data_flows_to": "vanta",
      "mechanism": "Vanta Rippling integration (HRIS, MDM, background checks)",
      "what_syncs": [
        "Active and terminated employees with name, work email, title, department, employment type, start and end dates, and status",
        "Leave data, when the connecting user can read leaves",
        "Desktops and laptops with a serial number: encryption, screen lock, password manager, antivirus and installed software",
        "Background check status"
      ],
      "plan_requirements": "Rippling full admin to authorize, and Rippling's IAM product on the account. Each Rippling product selected in Vanta (HRIS, MDM, background checks) must be active in Rippling.",
      "notes": "Vanta writes no records to Rippling; it only asks Rippling to generate device and background check reports, which it then reads. Vanta connects one HR system at a time, and imports employees active on or after a cutoff date set during setup. Mobile devices are not synced, and background checks run through Rippling's Checkr integration are not supported.",
      "source_urls": [
        "https://help.vanta.com/en/articles/11345682-connecting-vanta-rippling",
        "https://www.vanta.com/integrations/rippling"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#rippling__vanta"
    },
    {
      "pair": "salesforce__stripe",
      "tool_a": "salesforce",
      "tool_a_name": "Salesforce",
      "tool_b": "stripe",
      "tool_b_name": "Stripe",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Stripe app for Salesforce Platform; Salesforce Billing Extension",
      "what_syncs": [
        "Stripe Billing objects synced as Salesforce custom objects",
        "Activated Salesforce orders create Stripe subscriptions",
        "Salesforce quotes converted to Stripe subscriptions",
        "Stripe events mapped to Salesforce objects and fields",
        "Stripe API actions available in Flow and Apex"
      ],
      "plan_requirements": "",
      "notes": "The app is a builder toolkit used through Salesforce Flow Builder and Apex, so most syncs need configuration. The older Stripe app for Salesforce Billing is deprecated and Stripe points users to the Salesforce Platform app; the Salesforce Billing Extension adds card and ACH payments on Salesforce Billing invoices.",
      "source_urls": [
        "https://docs.stripe.com/use-stripe-apps/stripe-app-for-salesforce/overview.md",
        "https://docs.stripe.com/connectors/salesforce"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#salesforce__stripe"
    },
    {
      "pair": "salesforce__tableau",
      "tool_a": "salesforce",
      "tool_a_name": "Salesforce",
      "tool_b": "tableau",
      "tool_b_name": "Tableau",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "salesforce",
      "data_flows_to": "tableau",
      "mechanism": "Tableau Salesforce connector",
      "what_syncs": [
        "Any standard or custom Salesforce object into Tableau extracts"
      ],
      "plan_requirements": "Tableau Creator license (Tableau Cloud Standard is $75 per user per month billed annually).",
      "notes": "Extract only, no live connection. Tableau Cloud refreshes hourly at most. Incremental refresh covers the last 30 days; long text fields and formula fields are not extracted.",
      "source_urls": [
        "https://help.tableau.com/current/pro/desktop/en-us/examples_salesforce.htm",
        "https://www.tableau.com/pricing/cloud"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#salesforce__tableau"
    },
    {
      "pair": "salesforce__vanta",
      "tool_a": "salesforce",
      "tool_a_name": "Salesforce",
      "tool_b": "vanta",
      "tool_b_name": "Vanta",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Vanta Salesforce (Access) integration and Vanta Trust Center Salesforce integration",
      "what_syncs": [
        "Salesforce users with profile, role, active status, permission sets, permission set groups and last login into Vanta access reviews",
        "Optional deactivation of offboarded Salesforce users by Vanta (users are deactivated, never deleted)",
        "Account, Contact, User and Opportunity records read by Vanta Trust Center for auto-approval, tag-based document access and revenue reporting",
        "Leads created in Salesforce for unmatched Trust Center viewers",
        "Trust Center activity logged as Salesforce Tasks on matching contacts and accounts"
      ],
      "plan_requirements": "Salesforce Enterprise, Unlimited or Developer edition, or Professional with the API access add-on; Essentials cannot connect. Vanta lists access management from its Plus plan and automated access management on Professional; Trust Center from Essentials, Advanced Trust Center on Professional. Vanta pricing is quote-based.",
      "notes": "Two separate integrations sharing one Salesforce tile. The authorizing user needs Approve Uninstalled Connected Apps; deprovisioning also needs Manage Internal Users. Vanta will not deactivate the user who authorized the connection. Trust Center tag values sync every 24 hours and only string fields can be mapped.",
      "source_urls": [
        "https://help.vanta.com/en/articles/16920330-connecting-vanta-salesforce-access",
        "https://help.vanta.com/en/articles/11345449-connecting-trust-centers-salesforce",
        "https://help.vanta.com/en/articles/16862970-salesforce-integration-permissions",
        "https://www.vanta.com/pricing"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#salesforce__vanta"
    },
    {
      "pair": "shopify__stripe",
      "tool_a": "shopify",
      "tool_a_name": "Shopify",
      "tool_b": "stripe",
      "tool_b_name": "Stripe",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "shopify",
      "data_flows_to": "stripe",
      "mechanism": "Shopify Payments (built on Stripe) or the Stripe Card Payments payment provider",
      "what_syncs": [
        "Card payments, refunds and chargebacks handled inside Shopify via Shopify Payments in 41 countries",
        "Authorize, capture, void and refund through Stripe Card Payments where Shopify Payments is unavailable"
      ],
      "plan_requirements": "Any Shopify plan. Stripe Card Payments adds a Shopify third-party fee of 2% (Basic), 1% (Grow) or 0.6% (Advanced).",
      "notes": "Stripe Card Payments is added under Settings > Payments and replaced the legacy Stripe provider (migration deadline August 31, 2025). With it, disputes stay in Stripe. The Stripe Subscriptions App Store app is for billing, not checkout.",
      "source_urls": [
        "https://help.shopify.com/en/manual/payments/shopify-payments/supported-countries",
        "https://support.stripe.com/questions/update-shopify-payment-provider-from-stripe-to-stripe-card-payments",
        "https://apps.shopify.com/stripe-billing"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#shopify__stripe"
    },
    {
      "pair": "shopify__xero",
      "tool_a": "shopify",
      "tool_a_name": "Shopify",
      "tool_b": "xero",
      "tool_b_name": "Xero",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "shopify",
      "data_flows_to": "xero",
      "mechanism": "Shopify integration by Xero",
      "what_syncs": [
        "Sales as daily summaries or individual sales",
        "Shopify Payments and other gateway payouts",
        "Fees, refunds, and taxes",
        "PayPal transaction fees",
        "Online store and Shopify POS sales"
      ],
      "plan_requirements": "Requires a Xero account. Xero describes the integration as free and states no plan tier.",
      "notes": "The integration does not account for US sales tax, so that data has to be taken from Shopify directly for reporting and filing. The Xero page does not describe any data written back to Shopify.",
      "source_urls": [
        "https://www.xero.com/us/partnerships/shopify/"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#shopify__xero"
    },
    {
      "pair": "shopify__zendesk",
      "tool_a": "shopify",
      "tool_a_name": "Shopify",
      "tool_b": "zendesk",
      "tool_b_name": "Zendesk",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Zendesk Shopify integration for Support and Chat",
      "what_syncs": [
        "Order list and summaries in the ticket sidebar",
        "Order date, value, payment and fulfillment status",
        "Shipment tracking numbers and line items",
        "Refunds sent from Zendesk to Shopify",
        "Order cancellations sent from Zendesk to Shopify",
        "Tags added to tickets after refund or cancel"
      ],
      "plan_requirements": "Zendesk Suite Team, Growth, Professional, Enterprise, or Enterprise Plus; or Support Team, Professional, or Enterprise with Chat.",
      "notes": "Shopify data shows only on saved tickets whose requester email or phone matches a Shopify customer. Cancellation works only for unfulfilled orders, and refund and cancel options must be enabled in Admin Center.",
      "source_urls": [
        "https://support.zendesk.com/hc/en-us/articles/4408837984026-Using-the-Shopify-integration-in-Support-and-Chat",
        "https://apps.shopify.com/zendesk"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#shopify__zendesk"
    },
    {
      "pair": "slack__vanta",
      "tool_a": "slack",
      "tool_a_name": "Slack",
      "tool_b": "vanta",
      "tool_b_name": "Vanta",
      "status": "native",
      "direction": "both",
      "data_flows_from": "",
      "data_flows_to": "",
      "mechanism": "Vanta Slack (Access) integration; Vanta Slack Notifications integration",
      "what_syncs": [
        "Slack workspace members imported into Vanta",
        "Member email, admin status, and 2FA enrollment",
        "Vanta notifications posted to chosen Slack channels",
        "Personal Vanta alerts sent as Slack direct messages"
      ],
      "plan_requirements": "Vanta recommends connecting the access integration with a Slack Owner or Admin account. Workspace app approval may be needed to install the Vanta app.",
      "notes": "Two separate integrations: the access integration imports workspace accounts for access reviews, and the notifications integration posts Vanta alerts to channels. Private channels need the Vanta app added before they can be selected, and personal direct messages rely on matching email addresses.",
      "source_urls": [
        "https://www.vanta.com/integrations/slack",
        "https://help.vanta.com/en/articles/11345744-setting-up-slack-notifications",
        "https://help.vanta.com/en/articles/15971608-connecting-vanta-slack-access"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#slack__vanta"
    },
    {
      "pair": "snowflake__vanta",
      "tool_a": "snowflake",
      "tool_a_name": "Snowflake",
      "tool_b": "vanta",
      "tool_b_name": "Vanta",
      "status": "native",
      "direction": "a_to_b",
      "data_flows_from": "snowflake",
      "data_flows_to": "vanta",
      "mechanism": "Vanta Snowflake integration",
      "what_syncs": [
        "Snowflake user accounts",
        "MFA status for Snowflake users",
        "Inventory of databases holding user data",
        "Data warehouse ownership and documentation tracking"
      ],
      "plan_requirements": "",
      "notes": "The listing describes read and monitoring activity only. No writes to Snowflake are described.",
      "source_urls": [
        "https://www.vanta.com/integrations/snowflake"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#snowflake__vanta"
    },
    {
      "pair": "vanta__zendesk",
      "tool_a": "vanta",
      "tool_a_name": "Vanta",
      "tool_b": "zendesk",
      "tool_b_name": "Zendesk",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "zendesk",
      "data_flows_to": "vanta",
      "mechanism": "Vanta Zendesk integration",
      "what_syncs": [
        "Zendesk ticket data for security issue tracking",
        "Zendesk account information",
        "P0 to P3 security issue SLA checks",
        "Accounts compared against current employees"
      ],
      "plan_requirements": "",
      "notes": "The listing describes monitoring and testing only and does not mention Vanta creating tickets in Zendesk.",
      "source_urls": [
        "https://www.vanta.com/integrations/zendesk"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#vanta__zendesk"
    },
    {
      "pair": "vanta__zoom",
      "tool_a": "vanta",
      "tool_a_name": "Vanta",
      "tool_b": "zoom",
      "tool_b_name": "Zoom",
      "status": "native",
      "direction": "b_to_a",
      "data_flows_from": "zoom",
      "data_flows_to": "vanta",
      "mechanism": "Vanta Zoom integration",
      "what_syncs": [
        "Zoom user accounts",
        "Zoom user roles",
        "Account data used in user access reviews"
      ],
      "plan_requirements": "",
      "notes": "Listed under communication platforms and built by Vanta. The listing shows no supported resources or tests, so the scope appears limited to access tracking.",
      "source_urls": [
        "https://www.vanta.com/integrations/zoom"
      ],
      "checked": "2026-11-11",
      "url": "https://integratestack.com/data#vanta__zoom"
    }
  ]
}