Paragon

ActionKit is one API and MCP server giving an agent hundreds of integration actions across Paragon's connectors, with a uniform interface, agent optimized action schemas and real time execution. The Connect Portal handles OAuth and API key authorization per end user, so each action runs as that user and agents take authenticated action in the user's own SaaS tools.

Sourcedocs.useparagon.com/learn/actionkitread 2026-09-22

Workflows is Paragon's embedded iPaaS for event driven automations, with integration logic authored in TypeScript or a low code editor. A workflow can start from the customer's app, third party webhooks, an integration enabled event, a scheduler or another workflow, and API resources supply reusable triggers and steps. Steps are sequenced, branched and routed deterministically, executions can be reviewed step by step in Monitoring, and CI/CD and Git repo sync are supported.

Sourcedocs.useparagon.com/learn/workflowsread 2026-09-22

Managed Sync runs fully managed ingestion pipelines over each end user's third-party sources (files, CRM records, tickets, accounting data) with automatic backfill, incremental sync, failure recovery and normalized schemas, scaling to hundreds of millions of records, and a Permissions API enforcing the source system's access control on the ingested data for RAG; records and file content are then queryable through the Sync API. The synced store persists, scales past any context window and stays queryable.

Sourcedocs.useparagon.com/learn/managed-syncread 2026-09-22

End users authorize each integration for themselves in the Connect Portal and can be shown or particular workflows through Workflow Permissions, and the customer controls which actions its product exposes. Those settings limit what an agent may do, but no step where a person reviews, approves or validates an agent action before it commits is documented.

Sourcedocs.useparagon.com/connect-portal/workflow-permissionsread 2026-09-22

The homepage states SOC 2 Type II, HIPAA and GDPR compliance, the plans list GDPR and SOC 2 compliance as a feature, and a Trust Center and security documentation cover encryption standards, access control and a signable DPA. On the access side there is SAML based SSO on Enterprise, managed OAuth and API key authorization per end user through the Connect Portal with signed user tokens, and workflow permissions restricting which users or groups see which integrations.

Sourceuseparagon.com/pricingread 2026-09-22

Monitoring gives per-event visibility across the integration stack: searchable atomic logs of every project event, ActionKit tool-call logs with payloads inspected in real time, trigger subscription events and payloads, workflow executions with step-by-step breakdowns and failure details, and a Connected Users dashboard of each user's connection health. Events route to the customer's own stack through Event Destinations (Slack, Datadog, New Relic, Sentry) and the Task History API.

Sourcedocs.useparagon.com/monitoring/overviewread 2026-09-22

Each connected user's authorization and synced third party records persist, but no memory layer that keeps an agent's state or a user's context across runs is documented in Managed Sync, ActionKit, Workflows or the docs. The synced data store holds records, not agent memory with a stated scope or lifetime.

Sourcedocs.useparagon.com/learn/managed-syncread 2026-09-22

Hosting runs either in Paragon's own cloud or entirely on the customer's infrastructure. The docs carry an on premises hosting section with a managed instance configuration, and the pricing page lists self hosting and forward deployment on Enterprise.

Sourcedocs.useparagon.com/on-premise/hosting-paragon-on-premiseread 2026-09-22

The connector catalog and action library give an agent actions to call, which is integration capability rather than a packaged asset, and the use case library publishes implementation guides rather than assets a buyer adopts. No ready made workflows, templates or role specific agents of Paragon's own are documented.

Sourceuseparagon.com/use-case/libraryread 2026-09-22

Third party events are forwarded to the customer's agent so it can work in the background and respond to what happens in a user's tools, with one API to subscribe to any user integration event and normalized webhook policies across integrations. Workflows can be started by app events, integration webhooks, an API resource webhook or a scheduler, so work begins without a person asking.

Sourceuseparagon.comread 2026-09-22

Paragon serves integration actions to whatever model or framework the customer runs. ActionKit is delivered as an API or MCP server with agent optimized schemas and is used from the customer's own agent code, and the product pages name no model of Paragon's own, so the model is the customer's choice throughout.

Sourceuseparagon.comread 2026-09-22

The platform is built for developers. Its APIs and SDKs include a front end Connect SDK, headless Connect Portal APIs, the ActionKit and Sync APIs with published OpenAPI specs, a Permissions API and a Task History API. Builders also get a custom integration builder, custom actions, a hosted demo environment and a self hostable MCP server.

Sourcedocs.useparagon.com/llms.txtread 2026-09-22

Changes move through Release Environments, which test and deploy them before production, and versioned releases name breaking changes. A hosted demo environment and an ActionKit playground let teams try actions, and logs help debug failures. No way to score a change, such as test cases, a pass rate or a judge verdict, is documented.

Sourcedocs.useparagon.com/deploying-integrations/release-environmentsread 2026-09-22

Paragon reaches third party apps through their APIs and its own connectors. No browser, desktop or remote computer session that Paragon runs for an agent is documented, and no headless fetch or third party browser engine is wired in.

Sourcedocs.useparagon.com/learn/actionkitread 2026-09-22