Developers & API
Clarify the data flow first. Then build the integration.
Which system should read or change which data? Check an existing connection first. For a custom integration, this brief helps define the scope and open technical questions.
Access and documentation
What to know before implementation.
This page provides technical orientation. A public API reference with approved endpoints, authentication and limits is not yet published here. Confirm these details with the team for your use case before planning development work.
- Existing connection
- Find your tool in the integration catalogue. A listing alone does not establish which data directions and actions are available for your workflow.
- Custom integration
- Describe the objects and actions you need. Ask about approved access, documented endpoints and a suitable test environment.
- Operations
- Clarify limits, error handling, repeated requests, interface changes and the contact for incidents.
Ready to fill in · no sign-up
One specific workflow is enough to start.
- Outcome: which task should the connection reliably complete?
- Data: which objects and fields move in which direction?
- Trigger: when does the workflow start, how often and at what volume?
- Permissions: who can read, change and approve the connection?
- Failure: what happens with missing data, duplicates or an outage?
- Acceptance: which test case shows that the connection works?
Describe your use case.
Name the systems involved and your intended data flow. This helps clarify the suitable access and next technical step.
Discuss the integration with the team