Field Mappings
How data is mapped between triggers and actions, with rules for scoping and defaults.
Field mapping is how data moves between steps in an automation. A trigger produces values; downstream actions consume them; the field mappings tell each action which upstream value to plug into which input.
Claude maps fields for you
You describe the workflow in plain language. Claude figures out which fields the downstream steps need, finds them in the trigger's output, and maps them across. You see the result in the automation editor once the automation is built.
You can adjust mappings the same way:
> Lowercase the email before creating the contact.
> Default the company name to "Unknown" if the source is empty.
> Use the customer's full name instead of just the first name.
Claude applies the change and saves a new version of the automation.
When Claude checks with you
If a mapping is genuinely ambiguous (two source fields could plausibly fill the same destination, or a required value isn't present anywhere upstream), Claude surfaces the choice and asks you which to use. Otherwise it picks a sensible default and keeps going.
Custom fields
Vendors often expose custom fields beyond the standard schema, and APIANT supports mapping to them the same way as standard fields. They show up in mappings when Claude builds against your data — no advance declaration, no standard-vs-custom distinction to track.
See also
- How Data Flows — the trigger → actions → state model that mappings sit inside
- Actions — what actions take in and emit