Automatic Script Examples in Planfix: Email and SMS
The easiest way to understand automation is through automatic script examples: small rules that each do one job. In Planfix, processes and scripts act like robots on a conveyor belt, carrying out operations on your tasks at the right moment. This three-minute video walks through the four blocks every script is built from, then builds two simple scripts you can repeat in your own account.
What you’ll learn: two automatic script examples
- Where automatic scripts are configured in Account management and how they join a task process and its status set.
- What the four setup blocks do: the event, the conditions, the delay and the actions.
- How to email a client automatically as soon as a task is marked as completed.
- How to send an SMS the moment someone types text into a task field.
- How to make a script log what it did in the task feed, so the history stays readable.
How to set up an automatic script in Planfix, step by step
Every script answers four questions: when, whether, how soon and what. The Planfix help describes how scripts, events and conditions work; here is the order the video follows. Scripts live in Account management, next to the task process they belong to.
Step 1. Name the script and choose the trigger event
In the process script list, click New script and give it a name and a description you will recognise later. In the first block, choose the event that starts the script: a task being created, modified or deleted, a particular task field changing its value, or a specific time arriving. The name matters more than it looks: a list of scripts called after what they do, such as “Notify the client upon task completion”, stays maintainable as it grows.
Step 2. Set the conditions
The second block holds the conditions the script checks. They are evaluated at the moment the event happens, and the script runs only when all of them are met. This is what keeps automation quiet: without conditions, every status change would fire the same script. In the first example, the event is a status update and the condition is that the new status is Completed.
Step 3. Decide when the script runs
By default a script runs immediately. The third block lets you postpone it: set a delay in the Execute script settings and the action happens after the time you specify. One option there decides what happens when the event repeats before the delayed action has run: a new triggering of the script in the task can restart the countdown, or each event can produce its own action.
Step 4. Choose the actions
The fourth block is the outcome. A script can send an email built from a template, send an SMS, change field values or add a comment to the task, and one script can carry several actions. Scripts act on behalf of a user or a robot you name. Two safeguards are worth knowing: the changes a script makes do not trigger that same script again, so chains cannot loop, and testing mode lets you check the conditions before the script goes live.
Example: notify the client when a task is completed
The first script in the video is called “Notify the client upon task completion”. The event is a task status update, the condition checks that the status has changed to Completed, and the script then performs a single action: it sends an email built from a chosen template, on behalf of the employee who marked the task as done. Nobody has to remember the closing message, and every client hears about completion the same way. It is a small, safe script to try first in a CRM built around your process.
Example: send an SMS straight from a task field
The second script is a little more involved. A text field called Send SMS is added to the task; as soon as somebody types into it and presses Enter, the field value changed event fires. The action is Send SMS, which goes out through one of the SMS services you can connect, and the client linked to the task receives the text on their phone. Both the recipient number and the message accept variables, so the client’s number and the words just typed are filled in automatically.
The script does not stop there. A second action adds a comment to the same task, noting that the SMS was sent to the client and repeating the message. Logging the event in the feed costs one extra setting and makes the task history worth reading later. Sending SMS needs a paid plan and a service connected under Account management → Integrations.
Who it’s for
- Support and service teams: a completion email that goes out the moment a request is closed.
- Sales: an SMS confirmation typed into one field instead of switching to a phone.
- Operations: field changes that move work forward without anyone watching for them.
- Account administrators: scripts named after their job, so a process stays readable as it grows.
- Small teams on the free plan: one script per process is enough to automate the step that gets forgotten most often.
FAQ
What can an automatic script do in Planfix?
A script is a sequence of operations on tasks or contacts tied to an event and a set of conditions. It can send an email from a template, send an SMS, change field values or add a comment, and a single script can combine several of these actions.
Do automatic scripts work on the free plan?
Scripts are available on all plans, and the number you can add to one process depends on your plan: the free version allows one script per process. Sending SMS is different, because integration with an SMS service requires a paid plan.
Can a script run after a delay instead of immediately?
Yes. A script runs immediately by default, but the third setup block can postpone it by a set time. You can also choose whether a repeated event restarts the countdown or produces an action of its own.
Start with one simple script
Pick the one message your team sends by hand every day and turn it into a script: one event, one condition, one action. From there, business process automation in Planfix grows a step at a time. For a longer walkthrough that adds buttons and deal stages, see CRM workflow automation. New to Planfix? Sign up to try it.
