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.
Limits
The app is developed by ActiveCampaign. The listing does not name the exact fields synced or describe any data written back to Shopify.
Airtable Slack automation actions and Slack notifications
Data direction
Airtable → Slack
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.
Limits
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.
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.
Limits
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.
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.
Limits
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.
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.
Limits
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.
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
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.
Limits
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.
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.
Limits
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.
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.
Limits
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.
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.
Limits
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.
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.
Limits
Read-only. Drata recommends a read-only administrator service account with access limited to the listed fields and Company Files folders.
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.
Limits
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.
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.
Limits
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.
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.
Limits
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.
Microsoft Teams Sync and Microsoft Teams LTI apps for Canvas
Data direction
Canvas LMS → Microsoft Teams
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.
Limits
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.
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.
Limits
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.
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.
Limits
Only tasks created from Drata controls, tests, or risks appear in Drata. Tasks created directly in ClickUp are not imported.
ClickUp tasks created from Vanta; Task status and priority tags tracked; P0 to P3 security issue SLA checks; ClickUp accounts compared against current employees
Limits
Listed under task management and built by Vanta. Setup steps are in the Vanta help article Connecting Vanta & ClickUp.
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.
Limits
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.
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.
Limits
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.
Docusign CLM for Salesforce (AppExchange package via Docusign Apps Launcher)
Data direction
Salesforce → DocuSign
What syncs
Salesforce record data into Docusign CLM agreement templates
Plan requirements
Paid Docusign CLM licence; pricing is quote-based.
Limits
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.
Drata GitHub Issues connection; Drata GitHub version control connection
Data direction
GitHub → Drata
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.
Limits
Drata reads from GitHub and does not change permissions there. Labels entered in Drata must match the labels used in GitHub.
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.
Limits
Read-only. Because of a HubSpot API limitation, a user must be both deactivated and deleted in HubSpot before Drata detects the removed access.
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.
Limits
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.
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.
Limits
The workspace to sync is chosen during authorization. Tickets created directly in the external tool are not imported into Drata's ticket view.
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.
Limits
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.
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.
Limits
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.
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.
Limits
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.
Drata Salesforce connection (User Access Review and CRM connection types)
Data direction
Salesforce → Drata
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.
Limits
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.
Drata Slack connection (Communication and User Access Review)
Data direction
Both directions
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.
Limits
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.
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.
Limits
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.
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.
Limits
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.
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
Limits
Most of the integration is read-only evidence collection. The one write described on the listing is creating tickets in GitHub Issues.
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.
Limits
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.
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.
Limits
Only individual Google Ads accounts can be connected, not manager accounts.
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.
Limits
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.
HubSpot record data added or updated as Google Sheets rows from workflows
Plan requirements
HubSpot Professional or Enterprise (workflows).
Limits
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.
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.
Limits
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.
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.
Limits
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.
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.
Limits
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.
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.
Limits
Deals are not supported. Attachments on HubSpot notes do not sync. Legacy app property updates can take 1 to 24 hours.
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.
Limits
Reporting covers only the most recent year of account data. LinkedIn Ads accounts that are on hold cannot be connected.
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.
Limits
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.
HubSpot connected inbox for Outlook; HubSpot calendar sync with Outlook Calendar
Data direction
Both directions
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.
Limits
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.
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.
Limits
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.
HubSpot NetSuite integration (HubSpot Sync Bundle in NetSuite)
Data direction
Both directions
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.
Limits
Each sync can be set up as one-way or two-way. A NetSuite production or sandbox environment can be connected.
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.
Limits
Tickets support document creation but not sync rules.
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.
Limits
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.
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.
Limits
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.
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.
Limits
Orders synced from Shopify cannot be edited in HubSpot. Order sync does not detect or merge duplicate records.
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.
Limits
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.
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.
Limits
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.
Stripe Data Sync app (built by HubSpot) and Stripe as HubSpot payment processor
Data direction
Both directions
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.
Limits
HubSpot Payments (US, UK, Canada) cannot be used alongside your own Stripe processor connection.
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.
Limits
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.
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.
Limits
Invoices created in HubSpot must be edited in HubSpot or the sync fails. Six currencies are supported, and only payments created after connecting sync.
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.
Limits
Participants are matched to contacts by email. Recordings and transcripts sync only when cloud recording and audio transcripts are turned on in Zoom.
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.
Limits
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.
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.
Limits
The app is developed by Intercom. Multiple Shopify stores can be connected to one Intercom workspace.
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.
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
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.
Limits
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.
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.
Limits
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.
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
Limits
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.
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.
Limits
No subscription created, updated or canceled events.
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.
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.
Limits
It is switched on or off for the whole workspace and cannot be set per event. Mapped values overwrite existing Pipedrive values.
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.
Limits
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.
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.
Limits
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.
NetSuite Connector for Salesforce (Oracle SuiteApp on Oracle Integration Cloud)
Data direction
Both directions
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.
Limits
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.
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.
Limits
Send to Notion works on channel messages, not thread replies. Notion pages cannot be updated from Slack.
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
Limits
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.
Vanta Okta API integration (separate Okta SSO and SCIM apps)
Data direction
Okta → Vanta
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.
Limits
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.
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
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.
Limits
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).
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.
Limits
Installed from the Zoho CRM marketplace. Deal stage changes need PandaDoc's Workato-based Zoho automations; deal amount does not sync natively.
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.
Limits
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.
Stripe app for Salesforce Platform; Salesforce Billing Extension
Data direction
Both directions
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
Limits
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.
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).
Limits
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.
Vanta Salesforce (Access) integration and Vanta Trust Center Salesforce integration
Data direction
Both directions
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.
Limits
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.
Shopify Payments (built on Stripe) or the Stripe Card Payments payment provider
Data direction
Shopify → Stripe
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).
Limits
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.
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.
Limits
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.
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.
Limits
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.
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.
Limits
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.
Zendesk ticket data for security issue tracking; Zendesk account information; P0 to P3 security issue SLA checks; Accounts compared against current employees
Limits
The listing describes monitoring and testing only and does not mention Vanta creating tickets in Zendesk.
Zoom user accounts; Zoom user roles; Account data used in user access reviews
Limits
Listed under communication platforms and built by Vanta. The listing shows no supported resources or tests, so the scope appears limited to access tracking.
In an MCP client, add https://integratestack.com/mcp as a remote server (Streamable HTTP). What the server logs is described in the privacy policy.
Corrections
Found an entry that is wrong or out of date? Email contact@integratestack.com with the pair and a vendor link that shows the correct fact. Confirmed corrections are published with a new checked date.