Tip: You can use filters for better results
This specific feature set is only available for customers with a Business plan or an Enterprise plan.
What are Custom Object Automated Actions?
With custom automated object automated actions you can automatize processes for your customized created model. They basically work the same as ticket automated actions, with the only difference, being that they only apply to your custom models.
You can think of automated actions as a sandbox for creating automation inside the Work place. The most common use of automated actions is automatically sending relevant information and updates to your end users.
By smartly configuring automated actions, model users are not burdened with unnecessary work, resulting in less organizational effort and allowing model users to focus on more important work. Our solution engineers can help you configure custom object automated actions to fully meet and match your exact business requirements.
Inside the Admin panel go to Automations → Automated Actions
1. How to design Custom Object Automated Actions
- Decide if your action should be directly active in the system after creation. If you want your action to be directly active, switch the active switch to the right. If you are just preparing the action for now toggle the active switch to the left.
- Enter a name for your custom object automated action. Please avoid special characters and use underscores as connectors, otherwise you may run into the issue, that you cannot save your action.
- (Optional) - Enter a description for your new custom object automated actions. If you make your description clear and distinctive now, you will make it easier to distinguish between different actions.
- Select the object from the object dropdown. The action will only apply for this specific model.
You can select between three different action types and even define multiple actions per object if desired:
- The Send email action sends out an email to a dedicated email audience. You can customize the email contents and use aliases by typing "@".
- The Create Info actions creates an ticket info. You can customize the ticket info contents and use aliases by typing "@".
- The Send SMS action sends out an email to a dedicated SMS audience. You can customize the email contents and use aliases by typing "@".
1.1 Send email action
The send email action will send an email (for a selected custom object) at a specific workflow trigger point. This specific workflow trigger point has to be configured inside Workflows (Coming later).
Inside the email action, you can configure Aliases. Aliases are placeholders that are replaced with field details(@) or a URL link (#) when the action is triggered.
- The From field should be already pre-filled with either the default Fieldcode sending address or, preferably, the SMTP email address. Therefore no need to fill this field.
- Enter a recipient address or addresses to which the email should be sent. You could also enter an alias or aliases here to ensure that the field details will be filled in automatically by the system.
- (Optional) - Enter carbon copy address.
- (Optional) - Enter blind carbon copy address.
- Enter the subject of the email.
- Enter the email content.
You can check if your action was created in the middle section.
- The trash button allows you to delete your action.
- In the middle section, you can also check if your action is currently activated.
1.2 Create info action
The create info action will create info (for a selected custom object) at a specific workflow trigger point. This specific workflow trigger point has to be configured inside Workflows (Coming later).
You can select between different info types.
Inside the info action, you can configure Aliases. Aliases are placeholders that are replaced with field details(@) or a URL link (#) when the action is triggered.
- Select an info type. You can pick an existing template or even use your own configured templates. You can customize your templates in value sets.
- Enter the info text, that should be displayed when this action is triggered.
- Click Save.
You can check if your action was created in the middle section.
- The trash button allows you to delete your action.
- In the middle section, you can also check if your action is currently activated.
1.3 Send SMS action
The Send SMS action will send an SMS (for a selected custom object) at a specific workflow trigger point. This specific workflow trigger point has to be configured inside Workflows (Coming later).
Inside the SMS action, you can configure Aliases. Aliases are placeholders that are replaced with field details(@) or a URL link (#) when the action is triggered.
- Enter a phone number, or use an alias to configure from whom the SMS should be sent.
- Enter a phone number, multiple phone numbers, or/and aliases to configure SMS recipients. You can add multiple phone numbers by inserting a comma between numbers. Do not forget the country code.
- Enter the SMS message content. Try not to make the message longer than 300 characters.
You can check if your action was created in the middle section.
- The trash button allows you to delete your action.
- In the middle section, you can also check if your action is currently activated.
