Learn
Which systems does VeroTX connect to?
259 pre-built connectors across 23 categories, each backed by a documented REST API. What the catalog covers, how connectors authenticate, and how every connector call is governed.
The short answer
VeroTX has 259 pre-built connectors across 23 categories, exposing 1,086 governed actions in total. Each connector was checked against the vendor's public developer documentation for at least one documented REST API endpoint. Core enterprise systems include SAP S/4HANA, SAP Ariba, Oracle Fusion Cloud ERP, NetSuite, Microsoft Dynamics 365 Finance and Operations, Salesforce, Workday HCM, ServiceNow, DocuSign, Arena PLM, SharePoint and Box.
Connectors let VeroTX read context from and write results back to the systems you already run. Your systems of record stay authoritative. VeroTX runs the process that crosses them.
What the catalog covers
Different products from the same vendor count as separate connectors because each one talks to a different system. SAP S/4HANA, SAP SuccessFactors and SAP Ariba are three connectors, and so are Workday HCM, Workday Financials and Workday Recruiting.
| Category | Connectors | Examples |
|---|---|---|
| ERP and accounting | 22 | SAP S/4HANA, Oracle Fusion Cloud ERP, NetSuite, Microsoft Dynamics 365 Finance and Operations, Sage Intacct, QuickBooks Online, Xero, SAP Concur |
| HR | 23 | Workday HCM, Workday Recruiting, SAP SuccessFactors, Oracle Cloud HCM, BambooHR, Greenhouse, HiBob, Personio, Cornerstone OnDemand |
| Marketing | 23 | Adobe Marketo Engage, HubSpot Marketing Hub, Salesforce Marketing Cloud, Klaviyo, Mailchimp, Contentful, Qualtrics XM Platform |
| Communication | 20 | Slack, Microsoft Teams, Zoom Phone, Webex, RingCentral, Dialpad, Aircall, 8x8, Genesys Cloud |
| E-commerce | 19 | Shopify, Shopify Plus, BigCommerce, Adobe Commerce, Salesforce Commerce Cloud, WooCommerce, Bloomreach |
| Cloud and infrastructure | 13 | Amazon Web Services, AWS IAM, AWS KMS, Microsoft Azure, Azure RBAC, Google Cloud Platform, Oracle Cloud Infrastructure |
| Office and productivity | 13 | Microsoft Word, Excel, PowerPoint, OneDrive, OneNote, Microsoft Planner |
| Project management | 12 | Jira, Asana, Linear, Monday.com, ClickUp, Procore |
| Support and service desk | 12 | ServiceNow, ServiceNow ITSM, Jira Service Management, Zendesk, Freshdesk, Intercom |
| Documents and storage | 10 | SharePoint, Box, Dropbox, Google Drive, Confluence, Notion |
| Risk and compliance | 10 | Dun and Bradstreet, LexisNexis Risk Solutions, LSEG World-Check, Middesk, CrowdStrike Falcon, Tenable Vulnerability Management |
| Treasury and close | 10 | Kyriba, J.P. Morgan Access, Bank of America CashPro, BlackLine, Plaid, Mercury |
| Payments and billing | 9 | Adyen, Braintree, PayPal, Chargebee, Bill.com, Razorpay |
| CRM | 9 | Salesforce, Microsoft Dynamics 365, HubSpot, Pipedrive, Freshsales |
| PLM and engineering | 8 | Arena PLM, PTC Windchill, Siemens Teamcenter, Dassault ENOVIA, Propel, Duro |
| Identity and access | 8 | Okta, Microsoft Entra ID, Google Workspace, OneLogin, Ping Identity, JumpCloud |
| Contracts and e-signature | 7 | DocuSign, Ironclad, Icertis, Adobe Acrobat Sign, Conga CLM, Dropbox Sign |
| DevOps | 7 | GitHub, GitLab, Azure DevOps, Jenkins, Datadog, PagerDuty |
| Email and calendar | 7 | Gmail, Google Calendar, Outlook Mail, Outlook Calendar, Calendly |
| Endpoint and devices | 7 | Jamf, Microsoft Intune, Kandji, Lansweeper, IBM Maximo Application Suite |
| Data and warehouse | 6 | Snowflake, Databricks, Google BigQuery, Amazon Redshift, Fivetran, Google Sheets |
| Procurement and spend | 3 | SAP Ariba, Basware, Tipalti |
| EDA and CAD | 1 | Altium |
How connectors authenticate
Each connector uses the sign-in method its vendor documents. Across the 259 connectors, the split is:
- OAuth 2.0 (authorization code): 80 connectors
- OAuth 2.0 (client credentials): 62 connectors
- API key: 57 connectors
- Bearer token: 28 connectors
- Basic authentication: 20 connectors
- Vendor-specific: 12 connectors
The connector directory lists the authentication type and the configuration fields each connector needs, such as tenant URL, client ID or API key.
How a connector call is governed
A connector is not a free-standing integration. Every call runs inside a WorkStream, under the same four controls:
- Credentials are held in the platform credential vault. Agents never see them.
- Every call runs as a step in a versioned WorkStream Playbook, so the rules that apply are the rules that were published.
- Actions that cross a policy threshold stop at a tollgate and wait for the named approver.
- Each call is written to the Execution Ledger with the inputs, the result and the Playbook version in force.
Where connectors are used
Procurement uses ERP, procurement and spend, contracts and e-signature, documents, risk and compliance, and email connectors. Finance Ops adds payments, treasury and close, and CRM. People Ops relies on HR, identity and access, and endpoint connectors. Engineering Ops uses PLM and engineering, project management and DevOps connectors.
The same connector serves every WorkStream that needs it, so a NetSuite connection set up for Procurement is reused by Finance Ops.
When a system is not listed
Any system with a REST API can be connected by building a connector in the connectors studio, and VeroTX also supports webhooks, MCP and event streams. For deep or unusual integrations, FDESK engineers build the connector alongside your team.
Where to next
Read deeper
Product and platform pages on the same topic, drawn from the VeroTX knowledge base.
Search everything in one place in the Research Center, or ask Veroli, which answers from the same knowledge base.