Use this feature to map your Gravity Forms fields into Asana custom fields—ideal for capturing details like project category, priority, cost, or any data that matters in your workflow.
Mapping these fields also enables you to trigger Asana custom rules, like automation’s based on status, priority, or custom value changes—helping streamline your workflow.
Which Custom Fields Are Supported #
- Any Asana custom field that is not read-only (such as IDs or calculated fields) can be mapped.
- The upcoming reference-type custom field is not currently supported.
How Mapping Works #
- In the feed settings, check “Show Custom Fields”—the page will reload.
- All selected projects will display their available custom fields below.
- Match each Gravity Forms field to its corresponding Asana custom field using the provided fields.
Mapping by Field Type #
- Single Select
- Each Asana select value will appear with a field map option. You can either map it directly to a fixed Asana value or link it to a Gravity Forms single‑select field.
- Fixed Value Mapping: Choosing this means every task will always receive that value. This is useful when you want to mark all tasks from a form the same way, such as setting Priority to High, often to trigger a custom rule. If you do this, you cannot map that same field to anything else. Trying to map the same value again, or map one Asana value to another (e.g., Medium → High), will result in a validation error.
- Dynamic Mapping: Instead of a fixed value, you can map Asana values to specific Gravity Forms field choices. For example, “High” maps to the form’s High option, “Medium” to Medium, and so on. Whichever value the entry has, the corresponding Asana value will be applied. Not every Asana value must be mapped—unmapped ones will simply remain blank. However, each mapped Asana option must link to a separate Gravity Forms choice in the same field to avoid conflicts.
- Multi Select
- Each Asana multi-select value will appear with its own field map option, allowing you to link values to Gravity Forms multi-select fields.
- Fixed Value Mapping: Functions the same as Single Select. If you map to a fixed Asana value, every task will always include that option. You cannot map one Asana value to a different one (e.g., High → Medium). Although here you can map multiple values (e.g. High → High and Medium → Medium).
- Dynamic Mapping: More flexible than Single Select. You can map different Asana values to different Gravity Forms fields, or map the same Asana value to multiple Gravity Forms choices. This makes it possible to apply multiple tags or attributes to a task based on the selections made in the form.
- Custom Date, Text, & Number
- These fields all follow the same mapping pattern. Using the Gravity Forms field map, you can connect any form field or entry property to an Asana custom field of the matching type.
- Custom Date: Map a Gravity Forms date field (such as an event or deadline) directly into an Asana Date-type custom field. Be careful to map the correct type to avoid unexpected or undesired results.
- Text: Map any free text or short answer field from Gravity Forms into an Asana text custom field. This is useful for notes, references, or unique identifiers.
- Number: Map numeric fields, such as budgets, hours, or quantities, directly into Asana number custom fields. Decimal precision for numbers is respected.
- People Fields
- These function the same way as the assignee and collaborator fields. A drop-down of all available users will be presented allowing you to select from there. Adding mapping capabilities is planned for this field along with the assignee and collaborators fields.
There will be a tooltip next to each custom field name reminding you what type it is and any other relevant info.
If a field type doesn’t match the expected Asana custom field type, the plugin will usually leave that custom field blank. In some cases, unexpected results may occur.
