Mapping Account Data Fields in Workflows

Last updated: August 27, 2026

Mapping Account Data Fields in Workflows

Category: Workflows & Automation

A workflow's Data Fields card previously only let you map values onto the project you were creating. Now the same card also lets you map values onto the project's account, and lets your project-level fields pull from the linked account's own CRM data — not just from the record that triggered the workflow.

How It Works

The workflow's Data Fields card (previously "Project Data Fields") is now split into two sections:

  • Project Data Fields — the existing behavior, mapping values onto the project being created.

  • Account Data Fields — new. Maps values onto the CRM-linked account, drawing from your organization's active Customer Account data fields.

For both sections, the From trigger object picker now offers two sets of fields side by side: the trigger record's own fields, and — when the workflow resolves a linked CRM account — that account's fields as well (shown as Account.<field name>). This means a project field can now be populated from data that lives on the account rather than on the specific deal or case that triggered the workflow.

How to Configure It

  1. Open the workflow's Data Fields card.

  2. Under Account Data Fields, map any of your organization's active Customer Account fields the same way you already map Project Data Fields.

  3. When choosing From trigger object as a source, look for entries prefixed Account. — these read from the linked account rather than the trigger record itself.

  4. Save your changes and publish the workflow version when ready.

Account-sourced fields are only offered when your workflow resolves the account from the trigger record dynamically. If the workflow uses a fixed, hand-picked account instead, the Account.* options won't appear — there's no CRM record to read them from.

A Few Things to Keep in Mind

This is fully backward-compatible. Existing workflows with project-only Data Field mappings keep working exactly as before — you don't need to touch anything unless you want to start using Account Data Fields.

A missing link or an unresolvable field never fails the run. If the account can't be resolved, or a specific field can't be read, that one field is skipped and noted in the execution log — the rest of the workflow, and the project it creates, still completes normally.

Frequently Asked Questions

Do I need to set up anything new to use Account Data Fields?
You need active (non-archived) Customer Account data fields already defined for your organization — the same fields you'd use anywhere else account data is tracked.

What happens if the linked account can't be determined?
Account field mappings are skipped for that run and logged — the workflow still completes and the project is still created.

Can I mix Account-sourced and trigger-object-sourced fields in the same Data Fields configuration?
Yes — each mapping (project or account) chooses its own source independently.