Object Scripts in Planfix: Automate Notifications
Object scripts in Planfix automate the routine steps a team otherwise repeats by hand: a script waits for an event in a task, checks the conditions you set and then acts. Every object describes its own type of task — a meeting, a deal, a request — and its scripts are configured inside that object, as the Help Center article on object scripts explains. This short video walks through the four blocks of a script and two working examples: an email to the customer and an SMS sent from a task field.
What you’ll learn: how object scripts automate routine work
- Where scripts live: in the settings of the object whose tasks they work on.
- The four blocks of every script: event, conditions, execution time and actions.
- How to start a script when a task status changes to Completed.
- How to send the customer an email built from a template, with the right sender and recipient.
- How to send an SMS from a task field and keep its text in the task feed.
How to set up an object script in Planfix, step by step
Step 1. Open the object’s scripts
Open Account management, go to Types of objects and add a new object or select an existing one. In the object settings, open the section with the scripts and add a new one. Besides the mandatory name and description, the setup consists of four blocks. Fields, statuses, scripts and buttons all belong to the same entity, so it helps to shape custom objects in Planfix first and automate them afterwards.
Step 2. Choose the event that triggers the script
In the first block you select the event that runs the script: creating, modifying or deleting a task, a change to a field value, or another event. In the first example from the video, the event is Task is modified and now meets the conditions.
Step 3. Define the conditions
In the second block you define the conditions for triggering the script. After the event occurs, Planfix checks whether the task meets them, and the script runs only when it does — for example, when the task status changes to Completed. Conditions are what keep one script tied to one stage of the process instead of firing on every edit.
Step 4. Decide when the script runs
In the third block you choose when the script runs and on whose behalf its actions are performed. By default it is triggered immediately, but execution can be postponed to a specific time when the process needs a pause, such as a follow-up the next morning.
Step 5. Specify what the script should do
In the fourth block you specify the actions: send an email, change a field value, add a comment, modify another task. There are many settings here, which is why the video moves straight to concrete examples. Add further actions if one event should produce several, then save the script.
Example: automatic customer notifications
An email when the task is completed
The video sets up a script called Customer notification. The event is Task is modified and now meets the conditions, and the condition is the task status changing to Completed. Planfix should trigger the script immediately. Its action sends an email built from the template you specify: the recipient is the task creator, and the sender is the person who changed the status to Completed. Save the script, and from then on every finished job reports itself to the customer without anyone remembering to write.
An SMS when a field value changes
The second example is an automatic SMS notification. A text field called Send SMS was added to the object beforehand, and the script’s event is a change to the value in that field. Type the text, press Enter, and Planfix triggers the script immediately: the message goes out through an SMS service connected to Planfix, and the recipient is the counterparty. The script can also add a comment with the same text to the task, so the work done with the customer stays visible in the task feed and can be reviewed later for quality.
Who it’s for
- Support and service teams: the client hears that a request is closed the moment its status changes.
- Sales: a short SMS confirmation sent from the deal, with its text saved in the deal’s feed.
- Operations and process owners: one script per stage, so handoffs do not depend on anybody’s memory.
- Team leads: comments left by scripts show what was sent to the customer and when.
- Small teams without a developer: event, condition and action are picked from lists, with no code to write.
FAQ
What are object scripts in Planfix?
An object script is a sequence of operations on tasks that Planfix performs automatically when a chosen event occurs and the conditions are met. Scripts are set up inside the object whose tasks they act on, which is the recommended way to build business processes in a Planfix account.
Can a script email the customer automatically when a task is completed?
Yes. Set the event to the task being modified so that it now meets the conditions, add the condition that the status equals Completed, and choose the action that sends an email from a template. You also pick the sender and the recipient, such as the task creator.
How many scripts can one object have?
Scripts are available on all plans, and the number you can add within one object depends on your plan; in the free version of Planfix, one automatic script per object is available. A bulk action inside a script applies to a maximum of 150 tasks that match its conditions.
Start with one routine step
Pick one message your team sends by hand every day and turn it into a script: one event, one condition, one action. Scripts sit alongside buttons and processes in business process automation in Planfix, and you can debug them in testing mode before anyone outside sees the result. If you are still shaping the object itself, see how custom object fields and statuses work. New to Planfix? Sign up to try it.
