Integrations

Integration claims should be exact or absent.

Pursenda will need clear compatibility language, but this staging site does not invent supported products or read/write capabilities.

Book a working session Contact

Only list native integrations after the supported read, create, update, and trigger behavior is verified.

Document what the connection can do and when it was last reviewed.

Use the working session to identify the systems that matter for the first version.

Why the page still exists

Technical and operational reviewers need a place to evaluate compatibility, even before the directory is ready.

Owner gate

Production-supported integrations, data providers, automation claims, and API details require owner approval before publication.

Next step

Map the workflow before the software promise gets bigger.

Use the working session to decide what the first configured version should include and what should stay out of scope.