Third-Party Delivery and Integrations

This area manages outbound integration delivery to external platforms. It is designed for controlled configuration, reliable execution, and auditable outcomes.

Core records

The integration area is built around four record types:

1. systems (destination connection profiles)
2. mappings (internal-to-external identifier mapping)
3. hook-configs (event-to-endpoint delivery rules)
4. logs (delivery history and outcomes)

Typical setup flow

1. Create the external system profile.
2. Configure authentication and transport details.
3. Define mapping rules and hook configuration.
4. Run a test delivery.
5. Submit and approve changes where workflow control applies.
6. Monitor live delivery results in logs.

Security and control rules

Sensitive integration setup is controlled by workflow actions:

• submit
• approve
• reject
• deny

Self-approval is blocked for sensitive records. Authentication data is stored protected, and exposed request headers are sanitized in logs.

Runtime behavior

Live deliveries are processed asynchronously so user actions do not block on partner response time.

The system distinguishes:

• temporary failures that can retry
• terminal failures that need configuration or data correction

Delivery logs show status and timing so teams can decide whether to wait, retry, or fix configuration.

Response mapping and external IDs

The platform can capture returned partner identifiers and persist them for later use. This is important for create flows where future updates must reference an external system key.

External ID bulk import support is available for:

• nations
• languages