Define and request an external integration
Give your contact the provider and product version.
After this taskThe request contains owners, scope and acceptance checks.
Starting conditions and inputs
Identify owners of both systems and the integration purpose.
Values for this task
entry_url, organization_id, external_system, record_types, directions, owners, source_url
Command sequence
open "$entry_url" && snapshot -i
# Outside browser: Agree with the operator on system, external IDs, read/write scope, update cadence and conflict handling.
snapshot -i
click "$integration_account" && snapshot -i
get text body
open "$source_url" && snapshot -i
get text bodyRef targets and expected results
| # | Command / ref | Target and verification |
|---|---|---|
| 1 | Outside browser | Agree with the operator on system, external IDs, read/write scope, update cadence and conflict handling. |
| 2 | click $integration_account | Integration account record |
| 3 | get text | Compare system, organization and connection scope with the agreement. |
| 4 | open | Integration test source record |
| 5 | get text | Read the external ID and field values for the test. |
Check the result
The request contains owners, scope and acceptance checks.
Resuming after interruption
Check the original request ID and outcome first. Do not resubmit while its result remains unknown.
Confirm the provider
Give your contact the provider and product version. Similar names or another contract from the same provider can have different capabilities. Confirm the exact operations supported.
Define data and direction
Define which customer, reservation, or transaction data moves in each direction. Specify creation, updates, cancellation, and conflict ownership. Connecting a service does not imply migration of all historical data.
Confirm access
Confirm account ownership, permissions, and permitted API use. Match personal-data fields to the organization’s reviewed scope. Share credentials through the designated secure channel.
Agree on acceptance checks
Agree on acceptance checks using source records on both sides. Test creation, edits, cancellation, and duplicate events. Name the failure contact and document manual alternatives for unsupported operations.