Motion Building: best practices

1. Build a draft of your desired motion. The intent of this draft is not to publish, but to serve as a template that can evolve (and be cloned) for testing and production

2. Ensure you have known test accounts in your systems of record (ie, SFDC) that you can use for motion testing so as not to disrupt normal account operations

3. For your first motion, Magnify recommends testing each step (through progressive cloning) to facilitate an understanding of any nuances specific to your tech stack and data configurations, as well as to focus troubleshooting. 

4. Once a step has been vetted, clone and add the next step- rinse, repeat until all steps have been tested. 

5. Typically, once a first motion has been built and tested, nuances of your stack will be understood and this type of testing can be reserved for new actions/systems in the future. 

6. Note: if/then statements cannot be deleted without deleting all downstream branches and nodes. 

7. Slack- you will need channel and user IDs to use Slack in automation. This can be added as fields in SFDC, if needed for customer-facing channels. For any users whom messages are sent on their behalf, you will need to have them authorize Magnify. 

8. Note: the default data refresh cycle during onboarding  is 2x/24 hours-> 9am + 4pm EST, 1x per day post-onboarding
   1. This is relevant for:
      1. understanding how/when accounts/users enter a segment 
      2. understanding how/when accounts/users pass through if/else or wait for trigger nodes 
9. Relative Date Calculations in Motions
   
   When building a Motion—whether in a Segment, Rule, or Action—any condition involving “X days” (such as “within the last 3 days” or “in 2 days”) uses a rolling 24-hour interval, not calendar days. The calculation is based on the exact time the Motion is executed or the time the account-user pair interacts with the Motion step.
   
   Here’s how it works in different parts of a Motion:
   
   1. Segment Example
   A Segment might include a filter like:
   “Renewal date is within the next 3 days”
   
   This is interpreted as:
   “Renewal date is within the next 72 hours from the moment the Motion runs.”
   
   So if the Motion runs at 2:00 PM on June 10, it includes any account with a renewal date before 2:00 PM on June 13.
   
   2. Rule Example (If/Else Condition)
   A Rule might check:
   “Trial end date is within the past 1 day”
   
   This is interpreted as:
   “Trial ended within the last 24 hours from when this Rule was evaluated for the account-user pair.”
   
   So if the Rule is evaluated at 10:00 AM, it includes any account whose trial ended after 10:00 AM the previous day.
   
   3. Action Example (e.g. Create Task in Salesforce)
   An Action might use Dynamic Inputs to set a due date:
   “Set task due date to 2 days after today”
   
   If the Salesforce Due Date field is a date-only field (i.e. it does not store time), then:
   The date is calculated by adding 2 full days to the timestamp when the Action is triggered for the account-user pair. The result is converted to a calendar date.
   
   Example:
   If the Action runs at 4:00 PM on June 10, the due date would be June 12
   (since June 10 → June 11 → June 12, disregarding time)
   
   Key Notes:
   •   “Days” = 24-hour periods, not calendar days.
   •   All calculations are based on the exact timestamp when the Segment, Rule, or Action is evaluated.
   •   Timezones are not currently factored into this logic—all times are based on the Magnify's internal time tracking.

Updated June 10, 2025 20:41