Skip to content
English
More support Sign in
Go to patchretention.com
  • There are no suggestions because the search field is empty.

Set Fields Action Block

Update contact fields and tags for segmentation and reporting.

What's in this article

 


Summary

The Set Fields block updates contact fields, tags, or custom data so your automations stay organized and easy to target.

 

When to use

  • Tag a contact as Visited, Member, or Interested: Season, VIP
  • Update lifecycle stage (Lead → Customer → Member)

 

 

Common triggers that feed into this block

  • Contact Created (new lead / import) → Set default lifecycle fields (Lead status, source, owner), apply starter tags, and initialize lead score.

  • Check-In Finished (visit) → Tag as “Visited,” update last visit date, increment visit count, and set a “next best action” field for follow-up.

  • Order Finished (purchase) → Update total spend, last purchase date, last product/category, and mark “Paid customer” or “Converted” lifecycle stage.

  • Contact Updated (field/tag change) → Write change-based values (store “previous vs new”), set intent flags (Interested = true), and stamp “intent updated” date.

  • Calendar Event (appointment booked) → Set booking status fields (Booked/Confirmed), store event type/date, and mark “needs reminder” or “prep complete” flags.

  • Membership Start / End → Set membership status, start/end dates, renewal window flags, and apply tags for onboarding or win-back sequences.

 

 

How it works

  • Choose the field (example: Tags).
  • Choose an operation: Insert, Remove, Remove all.
  • Select the value to add/remove.

 

 

Best practices

  • Use consistent tag names (simple words, same casing).
  • Don’t create a new tag for every seasonal programaign; reuse when it means the same thing.
  • Pair with Filter so staff can understand “why” someone is getting a message.

 

 

 

Tabs in this block

Editor

This is where you configure the block. After you change settings, save the block so the automation uses the updated configuration.

Stats

Stats populate after the block runs for at least one contact. For most blocks, Stats are mainly for quick troubleshooting (example: times triggered and last completed).

Task Log

The Task Log is the best place to troubleshoot a specific run. Each row is one task (usually one contact) that passed through this block.

  • Time: when the task ran
  • Run Duration: how long it took
  • Contact: click the person icon to open the contact profile
  • View Payload: click VIEW PAYLOAD to see all data passed through the automation for that task
  • Task ID: helpful for internal debugging and support

Warnings & Errors

  • Errors must be fixed before the automation can be enabled.
  • Warnings do not always block enabling, but they usually mean something is missing or risky.
  • If you see an error or warning banner, fix it in the Editor, then re-open the block to confirm it is cleared.