Process Automator Actions
List of available Process Automator actions. Actions provide the automation to run based on the document referenced in the trigger or process step.
Available actions
Some actions are core platform-based and can apply to most documents. Other actions are application-specific and have use cases that apply to only to the associated application and documents.
Platform-based actions
Action | Description |
---|---|
Set Field |
Sets the value of a standard or custom field in a document. All Process Automator objects (for example, requisitions, purchase orders, expense reports, and so on) are supported except for forms. All field types are supported except for the following:
|
Send Notification |
Sends a notification to a dynamic recipient list based on a trigger event. This action appears for the Document Event trigger for the following document types: Custom Objects and Sourcing Events. You can further define conditions that must be met for the notification to be sent. Once you select this action, you can select a published template for the designated document type. For more information, see Custom Notification Templates. Note
The Send Notification process can send notifications to up to 25 recipients per process. You can send up to 2,000 emails total per day. |
Launch Form |
Launches a form for recipients to complete. For more information, see Create and Manage Dynamic Form Mapping. Note
If a user group is added in the Form Recipient field, only the user group admin is designated as the original responder. Only the original responder can add new records to a form response. |
Add Tag / Remove Tag |
Tag or untags requisitions, invoices, and contracts based on document attributes using various trigger events. Tags must be set up in the Platform before using this action. For more information, see Tags. The Note field can use the default note defined for the Tag, or an entry in the Process Builder Note field will override the default tag note for the document being tagged. |
API Call Out |
Sends standard and custom object data to external API endpoints as an XML or JSON payload. You can send invoices, orders, custom objects and expense reports as a complete JSON or XML payload and you can apply an API response filter to send only the subset of data that you need when that document is approved. Customers can configure Process Builder actions to automatically push approved documents to specified endpoints when they are approved or issued. With this feature, you can transmit created and updated object data to customer systems of record (like an ERP or HRMS) and it can be used to drive additional processes outside of Coupa. For example, a custom object job form response could be used to initiate a service request in an external system or send a custom object vacation form request to the HRMS. Call Outs and API Filters must be defined ahead of time. You must define the call out first and then add the API filter to that call out. For more information, see Call Outs and API Response Filters. |
Add Form To Flow |
Adds a form to a guided flow. Only available when the trigger type is Option Selected. For more information, see Guided Forms. |
Add Assignment |
Assigns a req to a buyer or buyer group using any combination of trigger events and conditions. For more information, see Requisition Buyer Assignments. |
Application-based actions
Action | Description |
---|---|
Review Supplier |
Sends a survey to your users to rate suppliers. Responses contribute to the supplier scorecard. |
Add Assignment |
Assigns a particular user to a record to streamline management. |
Auto Dispute | Sends invoices back to suppliers when certain tolerance conditions have not been met. |
Launch Form - External Recipient |
Launches a SIM form for an external recipient, such as a supplier. This lets admins build a process where end users can request an update from a supplier, without the need for a buyer or supplier manager to intervene. For more information, see Create and Manage Dynamic Form Mapping. |
Send to sourcing using template |
Creates a sourcing event using a predetermined template. |
Invite Supplier |
Sends CSP invitations based on conditions set on Community.AI data. For more information, see Process Automator Action to Request Suppliers to Invoice via CSP. |
Actions per trigger type
The actions available are dependent on the selected document or button location.
Document/Button location | Supported Actions |
---|---|
Contract |
API Call Out, Add Tag, Launch Form, Remove Tag, Review Supplier, Set Field |
Expense Report |
API Call Out, Launch Form, Set Field |
Invoice |
API Call Out, Add Tag, Auto Dispute, Launch Form, Remove Tag, Review Supplier, Set Field |
Order |
API Call Out, Launch Form |
Requisition |
API Call Out, Add Tag, Launch Form, Remove Tag, Send to Sourcing using template, Set Field |
Risk Request |
Launch Form, Launch Risk Assessment |
SIM Form |
Launch Form, Start Risk Assess |
Sourcing Event |
Launch Form, Review Supplier, Set Field |
Supplier Data Table |
Launch Form, Launch Form - External Recipient |
Supplier Search |
Launch Form |
Requisition Line | Add Form To Flow |