Verified now
No named integration is listed as supported until behavior, authentication, limits, object scope, owner, and last test are recorded.
Integration planning
No named integration catalog until behavior is verified.
Pursenda uses the working session to identify the systems that matter, then scopes supported read, create, update, and trigger behavior before implementation. No named integration is published as supported on this public-beta site.
Verified named integrations: none published
Last page review: 2026-08-08
Scoped planning
Imports, exports, webhooks, inbox, CRM, enrichment, and spreadsheet paths are scoped per implementation.
Publication rule
A system name appears publicly only after repeatable behavior is tested and the owner approves the wording.
Request flow
Use the working session to name the systems, fields, direction, and business event the first version must support.
Learn moreVerification matrix
What must be true before a system name appears.
The public page is an integration planning route until a repeatable connection has an owner, behavior record, and last-tested date.
QuestionRecorded before buildRequired before public catalog claim
System and object scopeSystem name, objects, fields, required identifiers, owner, and source of truth.Approved wording that names exactly what objects are supported.
DirectionRead, create, update, trigger, import-only, export-only, or manual file handoff.No two-way sync language unless two-way behavior is tested.
Authentication and limitsCredential owner, token handling, rate limits, retry behavior, failure handling, and audit owner.Security and operations owner approval.
Last-tested factsTest date, test environment, sample object, result, known limits, and reviewer.A current last-tested record tied to the published capability.
Planning path
Start from the buyer's actual workflow.
A useful first version names the CRM, spreadsheet, inbox, enrichment source, import/export route, webhook, or workflow system that carries the relationship today. The scope decides what Pursenda must read, create, update, trigger, import, or export.
Publication boundary
Absent claims are intentional.
This page does not claim support for HubSpot, Salesforce, Gmail, Outlook, LinkedIn, enrichment providers, ad platforms, calendar tools, or any other named integration. Those names belong here only after verified behavior and approved wording exist.
Next step
Name the system before naming the promise.
Bring the workflow and the system that has to stay connected. Pursenda will scope the integration behavior before it becomes a public claim.