Connectors and mappings

An action connector belongs to an organization and carries a name, code, effective period, policy reference and active flag. An automation definition points to a connector, so the Integration Steward can tell which outside service context the automation expects. Connection readiness should be checked before a reviewed definition is executed.

Source mappings describe how an outside field maps to a target field, with source and target types, a transform rule, version and effective date. Those details matter when a provider changes an event format. A definition can retain its original version while the mapping record shows the change the team intends to apply to later work.

• Organization. Keep connector settings with the organization that owns the automation.
• Effective period. Review the connection’s active dates and policy reference before using it.
• Field mapping. Name the source and target fields and the rule that transforms the value.

Identify the service owner for every outside connection and decide which system owns each field. Agree how credentials are stored and rotated in the approved secret store. The connector record describes the business connection; the provider account and authentication still need to be configured for the customer. Define the mapping version and a test record that proves values arrive in the intended target type.

Choose a pilot connector whose provider can return a clear receipt. Confirm its organization, active period and policy reference, then test one mapped field. Check the received value against the source event and the mapping rule. Record a provider reference on the attempt or a receipt on the step so the run can be reconciled later.

A provider begins sending a revised status code. The Integration Steward reviews the source mapping and its version before the Automation Owner prepares a new definition revision. The Reviewer sees which connector and mapping context the revision will use. The Operations Operator then executes a known source record and checks the resulting receipt against the provider’s response.

If the test value maps incorrectly, preserve the failed or uncertain attempt and correct the mapping before repeating the work. Do not overwrite the old receipt to make the pilot appear clean. This separation helps the team distinguish a bad transformation from a provider outage or a change to the automation itself.

• Active connectors — Check the connection name, organization and operating period.
• Definitions by status — Find the definitions that point to a connection.
• Failed attempts — Investigate provider references and failure reasons after a connection change.

See durable execution and receipt and exception review for the connected run.