Skip to main content

Set Field Values

Set Field Values Action

Set Field Values Action

Set Field Values writes to a field on the contact, on the contact's Account, or on one of the contact's Opportunities whenever the event that runs the action happens. Copy a value from one field to another, stamp a date, build a value out of several fields, clear a field out, and do any of it only when a condition holds. One action can set as many fields as you need: click Set Another Field Value to add the next one.

Choose the Field to Set​

For each field value, answer Which type of field would you like to set? with A Contact Field, An Account Field, or An Opportunity Field, then pick the field from Field Name. Only fields you have permission to edit are offered.

Opportunity Fields​

A contact can be on several opportunities, so when you set an Opportunity field you also tell Paminga which one with Which opportunity?:

  • Most recent open opportunity
  • Most recent opportunity (any status)
  • Opportunity where contact is primary (newest)
  • Primary if available, else newest open

A contact with no opportunity that matches the rule is skipped for that field. The same picker appears anywhere else in the action you read from an Opportunity field.

Where the Value Comes From​

Once you've picked the field, choose how its new value is decided.

Use a Specific Value​

Type or pick the value, and every contact the action runs on gets it. The input matches the field's type: a date picker for a date, a drop-down's own options for a drop-down field, True and False for a true/false field.

Use the Value From Another Field​

Copy the value from a contact, Account or Opportunity field into the field you're setting. Choose where it comes from, then pick the Source Field. Only fields whose type fits the target are listed: a number field takes numbers, a date field takes dates, and a text field takes nearly anything.

For a number or date target, check Then add or subtract a number (or Then add or subtract days) to adjust the copied value on the way in. Copy a renewal date and add 30 days to it, for example.

If the source field has no value? decides what happens when there is nothing to copy:

  • Skip the contact leaves the field as it is.
  • Set a fallback value writes the value you give instead.

Combine Multiple Fields​

Available for text, email, phone and website fields. Write the value the way you want it to read and insert fields where they belong, for example Hi [First Name], welcome!. Each contact gets the text with their own values filled in.

Clear This Field​

Removes the field's current value. Time Zone and Primary Language can't be cleared this way; see the note below.

Only Apply This Change When a Condition Is Met​

Check Only apply this change when a condition is met to make the change depend on another field. Choose a Condition field (contact, Account or Opportunity), an Operator such as is, is not, contains, is greater than, is before, is set or is not set, and the Value to compare against. The operators on offer follow the condition field's type.

If the condition is not met? works like the fallback above:

  • Skip the contact leaves the field as it is.
  • Set a fallback value writes the value you give instead.

Each field value carries its own condition, so one action can set a Lead Status only for contacts in a given country and stamp a date on all of them.

Fields With a Fixed Set of Values​

Most contact fields take whatever you type. Two do not, and the action gives you a picker for each rather than a text box: Time Zone and Primary Language.

Both hold a standardized code — an IANA time zone identifier like America/Denver, and a language tag like ES or FR-CA. A value outside those sets is not stored, so the picker is how you know the value you chose will actually land. You can search either list by typing.

note

The picker starts empty rather than on your own time zone. The value you set here describes the contacts the action writes to, not you.

If you copy the value from another field instead of choosing one, a language name is accepted and normalized on the way in — a CRM field holding French is stored as FR. The same is true for time zone casing: america/new_york is stored as America/New_York.

This action cannot blank either field

An empty value is neither a valid time zone nor a valid language, so leaving the picker empty sets nothing — it leaves whatever the contact already had. That is deliberate: a blank time zone breaks date rendering in emails, and a blank language is not the same fact as "we don't know theirs". To remove a value, clear it on the contact's Contact Details page.

Product

PricingFAQPaminga vs. MarketoMigration CenterMarketo to Paminga TranslatorMarketo Alternative
Paminga Logo
LinkedInFacebookXYouTube
ISO 27001 CompliantSOC 2 Compliant

Built with pride in Denver, Colorado, USA

Copyright © Paminga, Inc. 2026
All rights reserved. Various trademarks held by their respective owners.