Bring your CRM, ERP, finance, and everyday tools into a defined Proto workflow. Use the application’s interface, an approved API or CLI, or a configured MCP server.
SalesforceSAPOracleSageAnd the rest of your stack.
Find your systems.
Explore 30 enterprise integration targets. Each external connection needs configuration and validation for your software edition, permissions, and workflow.
Sales Cloud & CRM
Salesforce
CRM & service
Example workflow
Review account context, prepare opportunity updates, and follow up on outstanding customer actions.
Connection options
Use an approved Salesforce REST API or configured MCP server. Check your organisation’s API access, scopes, and record permissions. Browser workflows can be evaluated against your signed-in application.
Compare purchase orders, investigate order exceptions, and prepare operational summaries.
Connection options
Scope the connection to your SAP product and deployment. Published OData or SOAP services need communication configuration and permissions. Web and native SAP clients require separate workflow validation.
Review finance and procurement records, explain exceptions, and prepare reconciliation work.
Connection options
Connect approved Fusion REST resources through configured tools or scripts. Select the relevant application, security roles, and permitted actions for your tenant.
Check invoices, compare ledger entries, and prepare finance exception reports.
Connection options
Assess Sage Intacct’s REST API and your Web Services subscription. Other Sage products, including X3 and desktop editions, need their own connection assessment.
Investigate order and finance exceptions, compare entity records, and prepare reports.
Connection options
Use published Finance and Operations OData or JSON services with approved OAuth access. Sales, Business Central, and other Dynamics applications have different interfaces to validate.
Investigate manufacturing order exceptions and prepare purchasing or inventory reviews.
Connection options
Expose approved Kinetic REST services, business objects, or functions through configured tools. Validate the version, service account, and permitted operations.
Summarise support history, organise ticket context, and draft responses for review.
Connection options
Use the Ticketing API or a configured MCP server with approved access to tickets, users, and organisations. Validate update and reply permissions separately.
Prepare payroll exception reviews and check approved employee-data transfers.
Connection options
Assess the APIs available for your ADP product and customer or partner arrangement. Payroll actions and sensitive records need a defined permission scope.
Prepare meeting briefs, find supporting documents, and draft messages or reports.
Connection options
Use approved Microsoft Graph scopes through a configured tool or MCP server. Tenant consent and application permissions determine the accessible services and actions.
Bring messages, documents, spreadsheets, and meeting context into a working brief.
Connection options
Configure the relevant Workspace APIs and OAuth scopes, or an approved MCP server. Check administrator policies and each application’s available actions.
Try a product name or a different workflow, or clear the filters to see the full directory.
The examples describe workflows to scope during setup. Available actions depend on the application, credentials, and connection. Browser workflows are evaluated in the target interface; API and MCP routes require an approved tool or adapter. Read the connection guide.
A connection that fits the work.
Start with one task and the smallest set of permissions it needs. Confirm the result in the system where the work happens.
01 /Browser
Work through the interface.
Evaluate a workflow in a signed-in web application. Confirm the account, available controls, and saved result. Authentication and interface behaviour vary by product.
02 /APIs & tools
Use approved operations.
Configure vendor APIs, installed command-line tools, or an MCP server for a defined set of actions. Keep credentials and permissions scoped to the task.
03 /Your environment
Respect the network boundary.
Validate private endpoints, repositories, and self-hosted applications in your environment. Public SaaS requires network access; air-gapped deployments can only reach internally available services.
Start with your workflow
Your system isn’t listed?
Bring the product name, deployment type, and task you want Proto to handle. We’ll scope the available interface and the integration work.
Essential cookies run Proto. Choose whether we can remember your preferences and measure site use.Essential cookies run the site. Optional cookies are your choice.
See Cookie policy
Manage Your Cookie Preferences
Proto uses essential cookies and, if you choose, remembers your preferences and measures site use.
You can change this choice at any time.
Your browser's Global Privacy Control signal is honored: advertising cookies are off.