Before you create Auto Actions, read this

It's helpful to have a few things organized before you create a new Auto Action in SAM.

Write out what the Auto Action is supposed to do

List what you'd like the Auto Action to do (be specific). Here are some examples: 

Example 1: "I want an email to go to the family after they submit our application form."

What's the trigger? The application is submitted and the Application Received Date field is updated

What action happens? An email is sent to the Family

Example 2: "I want SAM to change the Case Stage to Application when the "Application Received Date" is entered in the family's record."

Trigger: The Application Received Date field is updated. 

Action: SAM updates the Case Stage from Inquiry to Application. 

What table will your Auto Action be triggered from? 

If you're creating an Auto Action and the trigger based on the placement date of a Child record, you would click on the plus sign next to Child > Adoption > Placement Date. In our example, our Auto Action trigger is the Application Received Date, which is on the Family Case table.

Name your Auto Actions consistently

Decide on a consistent way that your organization will name Auto Actions so that they describe what the Auto Action is for and what it's doing. There are several examples already loaded into SAM. You can name your Auto Actions whatever you want, but keep in mind that consistency will help keep you organized in the long run.

Here are a few examples:  

Case Stage Number | Case Stage Description | Action | Why Action is Being Done

-OR-  Action | What triggers the action

-OR-  Trigger | Auto Action | Why