Connection patterns
Match the transport to the responsibility.
Lead capture API
A server sends a customer enquiry directly to PeopleTide.
InboundRegistered web forms
A known form receives submissions and can trigger an explicit workflow.
InboundPBX / Asterisk
A phone system sends call lifecycle events with a stable call identifier.
OutboundREST connectors
PeopleTide reads approved data or completes a defined action in another system.
ManagedPeopleTide HMIS
A hospital approves locations and clinical capabilities through managed quick connect.
Design checklist
Define the contract before credentials.
- 01
Name the action
Describe one outcome such as create a lead, check availability, or create a support ticket.
- 02
Choose direction and authority
Decide which system owns each record and whether PeopleTide reads, writes, or receives an event.
- 03
Allowlist fields and operations
Expose only the data and actions required for the approved outcome.
- 04
Define failure behavior
Agree on timeouts, retries, idempotency, validation errors, and human escalation.
- 05
Test and observe
Run representative success and failure cases, then monitor delivery activity after launch.