Skip to content

ProcessScout integrations

Connect the context. Know the boundaries.

Start with the evidence your process needs. Every connector is in beta; see what each one does before you plan.

BetaImplemented operation in beta. Setup required; validate coverage for your account before relying on it.

HandoffArtifact or scoped implementation; not managed execution.

ProcessScout / TransformReal product · fictional data
The Sources view of a fictional project: the files and records a team brings in, each with its findings
Evidence lands in Sources and connects to the systems layer of the Digital Twin · real product, fictional data

Scope the connection

A system name is only the beginning.

Describe the job the connection must do. Permissions, operations and evidence quality can then be checked against it.

Name the records and direction.

Say which objects and fields matter, and whether the operation reads or changes them. A discovery export is a different commitment from a production write.

Name the identity and boundary.

Confirm which account grants access, what it can see and which projects may use the evidence.

Define a successful test.

Pick a representative record and its expected result. Check the output and unsupported fields before widening the scope.

Connection directory

Find your system.

Search by system or operation, then filter by support level.

Coverage reviewed October 12, 2026: an implementation guide, not a live connection-health check. Availability depends on your plan, permissions and provider setup; reading evidence does not imply write-back or workflow execution.

14 connections shown

Integration operations, support levels and setup requirements
System & supportSupported operationBefore you begin
Google WorkspaceBeta
Evidence syncImport supported Gmail and Drive content.OAuth consent and selected scopes; document access follows the connected account.
Microsoft 365Beta
Evidence syncImport supported mail and file content.Microsoft tenant consent and supported account permissions.
SlackBeta
Evidence syncRead permitted conversations and messages.Workspace installation and channel scopes determine coverage.
JiraBeta
Evidence syncRead projects, issues and their workflow context.Project permissions and an authorized Jira connection.
SalesforceBeta
Evidence syncRead supported CRM records, including leads and opportunities.API access, object permissions and a configured connection.
GitHubBeta
Evidence syncRead repositories, issues and pull requests.Installation or account access must cover the selected repositories.
QuickBooks OnlineBeta
Evidence syncImport supported invoices, bills and accounts.Company authorization and accounting data scopes.
XeroBeta
Evidence syncImport supported invoices, contacts and accounting records.Validate entity coverage and the sync result with your own organization.
NetSuiteBeta
Evidence syncImport supported ERP records.Account-specific roles, authentication and record coverage need validation.
SAP S/4HANAHandoff
Scoped integrationPrepare requirements for an implementation handoff.No supported native evidence sync is promised by this listing.
NotionHandoff
Scoped integrationScope a content integration with your implementation team.A handoff is not a live connector; agree the implementation separately.
n8nBeta
Workflow deliveryGenerate a native workflow for your team to import and review.Credentials, supported nodes and validation in your own n8n; your team decides when to publish.
MakeBeta
Workflow deliveryGenerate a blueprint for import and review.Complete account connections and validation in Make; no managed publication promise.
ZapierHandoff
Workflow deliveryGenerate a workflow handoff artifact.Complete setup and testing in Zapier; no managed deployment promise.

Start small

No connection required to start learning.

Bring a document, spreadsheet, browser recording or event log. A focused first project can begin with representative evidence.

From artifact to operation

Check each stage on its own terms.

Generating an artifact, publishing it and proving it works are different jobs, so the directory separates them.

Create or export

Inspect the generated artifact and its conversion findings. A native file can be a useful handoff even where publishing is not supported.

Configure and publish

Your team confirms credentials, settings and the exact version before it touches operational work.

Verify and recover

Check the result in the target environment and know the recovery path; rollback varies by provider.

Plan your connection

Check your integration scope.

Tell us the system, the records and the operation you need. We’ll confirm plan eligibility, permissions and setup with you.

Product view

ProcessScout interactive demo · Fictional Northstar data