Add Platform triggers to automate tasks

Anytime you have a recurring event related to a consistent change in record data, you can use a trigger. It might run on record creation, record update, or record deletion. For example, on a CRM application, you can use a trigger that sends an email to a manager when an opportunity is created or deleted. Or, you might send an email when the dollar value of the opportunity gets updated.

1. Go to Platform Services > Objects.

A list of all objects appears.

2. Find and select the object to which you want to add a trigger.
Can't find the object you're looking for?

Terms may differ from those used in your location when choosing an object in Customization Services and Platform Services. For information on terms that may differ in your location, see Terminology across locales.

Use the Filter by application dropdown list at the top of the page to filter by custom applications.
3. At the top of the Object Definition page, select Triggers.
4. In the Triggers section, select New trigger.

The New Trigger page displays.

5. Select a Trigger type that matches the type of action you want to perform.
   About trigger types.

   Trigger type details

   Trigger type	Details	Available in Custom Objects	Available in Standard Objects
   Validation	Sets rules about a particular field value and tests the input value before storing it in the database. When the user violates these rules, the trigger interrupts the record creation or update and returns an error message to the user. For example, in a CRM application where you do not want opportunities with low dollar values listed, you can set a validation rule. The rule can return an error message anytime a user enters an opportunity with a dollar value of less than $500.	Yes	Yes
   Change workflow status	Create at least one Workflow Status before using this event type.	Yes	No
   Update field value	Changes a specified value in this record or a related record. For example, a Customer Service application Customer object might have a date field called Most Recent Contact. When an entry for this customer is made in the related object, Service Requests, the Most Recent Contact field is updated with the current date.	Yes	Yes
   Create activity trail record	Enable the Audit Trail property for this object before using this event type.	Yes	No
   Create new record	Adds a new record using the conversion map specified for this trigger. For example, you might have an object of contacts called Leads. You could create a trigger that automatically creates a Customer record based on a lead when a sales quote is created.	Yes	Yes
   Attach related record	Sets a new relationship between records from two objects. For example, a payment record ID can be added to the original invoice record upon creation.	Yes	Yes
   Run triggers on related records	Invokes triggers on records in a related object. For example, you can write a set of triggers in a related object. Then, you can activate the triggers by a change made in the current object.	Yes	Yes
   Send email	Sends an email to a specified recipient or list of recipients. The email is based on an email template, so at least one email template must be created before using this trigger. Sending an email is a great way to alert decision makers automatically about application activity.	Yes	Yes
   Create template document	Create at least one File Upload field before using this trigger type. Generate a new payload document based on a document template and save it to a specific File Upload field in this record. You can use this document to make a Web Services call based on the object record.	Yes	No
   HTTP get	Calls a URL using the GET method. The URL is taken from an Integration Link field in the object. For example, you might want to post certain parameters to an external site by way of Get parameters. At least one Integration Link field is needed to use this Trigger type.	Yes	No
   HTTP post	Calls a URL using the POST method. For example, you might want to post values to an external site by way of Post value name pairs. At least one document template is needed to use this Trigger type. You can also use this trigger type to create a webhook. For more information about using HTTP Post for webhooks, see Outbound webhooks in the Sage Intacct Developer portal (REST API) .	Yes	Yes
   Intacct API	Sends a request directly to the Intacct API from a document template. The Intacct API type does not require an HTTP request because the trigger is executed within Intacct. You also do not need to include credentials for the API call, because Intacct uses the credentials of the current user.	Yes	Yes
   Event queue	Stores events so that you can retrieve them and get notifications on your schedule. See the Sage Intacct Developer portal (REST API) for information about using cURL commands to retrieve notifications.	Yes	Yes
   Intacct REST API	Sends a request to the Intacct REST API.	Yes	Yes

6. Select Next.
7. Make sure to select This trigger is deployed.
8. In the Trigger Activation section, select when this trigger will activate.

   Select at least one trigger activation option.

   Trigger activation option details

   Trigger activation option	Details
   Before create	Activates when a user adds a record before the record is posted.
   Before update	Activates when a user changes a record before the update is posted.
   Before delete	Activates when a user deletes a record before the record is deleted in Intacct.
   After create	Activates when a user adds a record after the record is posted.
   After update	Activates when a user changes a record after the update is posted.
   After delete	Activates when a user deletes a record after the record is deleted in Intacct.

    
9. Enter an easily identifiable and unique Trigger name.
10. For update triggers, select a specific field change that activates the trigger in Field to change. Any change in this value activates this trigger.

    For example, someone selecting an Approval box can change the status of the record from Concept to Project. Only a change in that field will activate the trigger. The default is to activate the trigger on any update.

    When you create a trigger, fields that might result in corrupt data do not appear as options for standard fields. Direct updates are only allowed on custom fields. Refer to Triggers field block list.

11. Optionally, select Run offline to run the trigger in the background while the user continues with their work.
    This option is not available for the Validation trigger type.
12. Set the remaining properties for each Trigger type. See Set trigger type properties for more information about the options.
13. In the Change Value Formula section, create a conditional expression that executes the trigger if it evaluates to true.
14. Select Save.