Skip to main content
Procesario

Integrations · Procesario Connect

Keep the systems that run your business. Connect the process between them.

Procesario reads event data from where work happens and writes back only through governed actions. The list below is the connector scope the platform is being built toward — each entry is labelled with its status.

Book a demoAsk about a connector

Principles

Four rules for how Procesario connects.

  1. 01

    Read from where the events already are — no desktop recording, no duplicate warehouse.

  2. 02

    Write only through typed, permissioned, logged actions.

  3. 03

    Keep the workflow engines, bots and agents you already run; make them executors in one governed loop.

  4. 04

    Model-neutral: the model provider is a setting, not a dependency.

Connector scope

By category.

No logos are displayed until a connector genuinely exists. Named systems are targets, labelled In development, Planned or Via partner.

  • ERP

    Source · executor

    Systems of record for orders, invoices, payments and deliveries — the primary event source and, through governed actions, an executor.

    • NetSuiteIn development
    • Microsoft Dynamics 365In development
    • Oracle Fusion CloudPlanned
    • SAP (via customer-owned replication or certified partner extractors)Via partner
    • InforPlanned

  • CRM

    Source · executor

    Customers, accounts, opportunities and cases — context for receivables and customer operations.

    • SalesforcePlanned

  • Databases

    Source

    Direct read access to relational stores where systems expose their tables.

    • PostgreSQLIn development
    • Microsoft SQL ServerIn development
    • Oracle DatabasePlanned

  • Data platforms

    Source

    Lakehouses and warehouses — the preferred substrate: Procesario is designed to compute against your data platform where possible.

    • SnowflakeIn development
    • DatabricksIn development
    • Microsoft FabricPlanned
    • Google BigQueryPlanned

  • APIs and event streams

    Source · executor

    REST and GraphQL for typed system actions; webhooks and streams for events as they happen; files for batch history.

    • REST / GraphQL actionsIn development
    • WebhooksIn development
    • Apache KafkaPlanned
    • CSV / Parquet filesIn development

  • Workflow and collaboration

    Executor

    Where people receive tasks, approvals and drafts.

    • EmailIn development
    • Microsoft TeamsIn development
    • SlackPlanned

  • Automation

    Executor

    Existing bots and flows become executors inside a governed playbook rather than islands.

    • UiPathIn development
    • Microsoft Power AutomatePlanned
    • Automation AnywherePlanned
    • CamundaPlanned
    • n8nPlanned

  • AI models and agents

    Executor

    Bring your own model keys and agent platform. Procesario supplies the context and the guardrails; models are interchangeable services.

    • Anthropic, OpenAI, Google and Azure OpenAI models (bring your own keys)In development
    • External agents via MCPIn development
    • External agents via A2APlanned

  • Service management

    Source · executor

    Tickets and cases as an event source and as a place to act.

    • ServiceNowPlanned
    • Coupa (procurement)Planned

Product names belong to their respective owners and are listed only to describe integration scope. Listing a system here does not imply a partnership, certification or endorsement.

Need a system that is not listed?

Tell us which systems run the process you want to improve. We will tell you plainly what is possible today, what is planned and what would need to be built.

Book a demoStart with one process