Answers.Body: <p>This exact thing came up for me this week.</p>
  <p>Just use the word &quot;now&quot;, without quotes. No json.</p>
  <p>It uses api3 to set the value so anything api3 understands will work.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-12-22T01:19:29.850Z
Answers.Text: YES! thank you, been looking for this answer for months.
Answers.UserDisplayName: Tim CD
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-04-21T15:48:26.957Z
Answers.LastActivityDate: 2023-04-21T15:48:26.957Z
Answers.UserDisplayName: Demerit
Body: <p>In a civirules action I would like to set a custom participant field to the current date/time using the action 'Set Custom Field on any entity'</p>
  <p>What json can I use for current date/time to set a custom date?
  (or might there be another smart workaround)</p>
  <blockquote>
  <p>$now() does not do the job</p>
  </blockquote>
  <p><a href="https://i.sstatic.net/YsI3J.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/YsI3J.png" alt="enter image description here" /></a></p>
  
Tags: <civirules><participants>
Title: JSON syntax to set custom date field with current date/time using a civirules action
ThreadText: # JSON syntax to set custom date field with current date/time using a civirules action
  
  (Asked by: username_0 on 2023-04-21)
  
  In a civirules action I would like to set a custom participant field to the current date/time using the action 'Set Custom Field on any entity'
  
  What json can I use for current date/time to set a custom date?
  (or might there be another smart workaround)
  
  > $now() does not do the job
  
  [![enter image description here](https://i.sstatic.net/YsI3J.png)](https://i.sstatic.net/YsI3J.png)
  
  **Tags:** civirules, participants
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2023-04-21. Score: 2
  
  This exact thing came up for me this week.
  
  Just use the word "now", without quotes. No json.
  
  It uses api3 to set the value so anything api3 understands will work.
  
  > **Comments:**
  > **username_2**: YES! thank you, been looking for this answer for months.  
  
  ---
  
  