Creatio.ai system actions
Creatio.ai comes with a set of system actions that it can use independently of the AI Skill it is currently handling. You can also use these actions in your own AI Skills as needed. The system actions are implemented as business processes.
The user must have permissions to perform the corresponding operations to use object data in system actions. Learn more: Object operation permissions.
This article contains the list of actions, describes the situations in which they are used, and provides examples of how you can use these actions in custom AI Skills.
List of actions
Name | Code | Description |
|---|---|---|
Get current date/time | Copilot_CurrentDateTime | Gets values of the current date and time in the UTC zone and the time zone offset of the user. |
GetDatesDiff | Copilot_DateDiffProcess | Gets difference between 2 days, in seconds. |
Parse date/time | ParseDateTime | Converts natural language date and time expressions into normalized ISO-8601 format with UTC and local time zone values. |
Copilot_GetCurrentUserInfo | GetCurrentUserInfo | Gets information about current user: full name, job title, phone, ID. |
Retrieve entity contextual data | QueryEntityData | Queries contextual data for the specified object. |
Get Entity Structure | Copilot_GetEntityStructure | Gets entity structure and returns the list of entity columns. |
Search Entities | Copilot_SearchEntities | Global search for Creatio records using keywords. Supports filters by name of the "Object" type schema. |
GetIndexedEntities | Copilot_GetIndexedEntities | Gets a list of object names that are indexed by global search. |
Contextual document provider action (SourceCode type action) | ContextualDocumentProviderAction | Code-based source code system action that enables developers to get content of text file documents. |
Create record default action | CreateRecordDefaultAction | Default action to create a record in Creatio object. |
Validate record before creation for object-level checks | ValidateRecordDefaultAction | Validates record data to ensure required fields and object-level business rules are met before creation. |
Usage examples
Creatio.ai uses system actions when executing various operations. View the operations below.
Work with dates
Actions: "Get current date/time," "Get Dates Difference," "Parse date/time."
You request to create something for next Tuesday. Creatio.ai uses the "Get current date/time" action.
You ask "How many days ago was this?" Creatio.ai uses the "Get current date/time" action followed by "Get Dates Difference".
You request to schedule a meeting tomorrow after lunch. Creatio.ai uses the "Parse date/time" action using "tomorrow after lunch" as input and returns corresponding date and time options: a date for the next day and a time after 1:00 PM.
Retrieve contextual information from the current page of the user
Actions: "Retrieve entity contextual data," "Get Entity Structure."
AI Skill mentions to read data from the Status page field. Creatio.ai uses the "Get Entity Structure" action to obtain the page structure and find the Status field. Then Creatio.ai uses "Retrieve entity contextual data" action to obtain data from the object based on a set of columns.
AI Skill that generates a summary includes "Get information from the page." Creatio.ai uses the "Get Entity Structure" action to retrieve the structure of the page. Then Creatio.ai uses the "Retrieve entity contextual data" action to gather data from the object based on specified columns.
Search through Creatio
Service: Global search.
Actions: "Search Entities," "Get Indexed Entities."
You ask Creatio.ai "Find me something about Project Management." Creatio.ai uses the "Search Entities" action to retrieve the search results.
AI Skill mentions "search Creatio for knowledge base articles based on keywords." Creatio.ai uses the "Get Indexed Entities" action to identify the entity to search. Then Creatio.ai uses the "Search Entities" action to retrieve the search results.
Gather information about the current user
Action: "Get current user info."
AI Skill requires user-specific data. Creatio.ai uses the "Get current user info" action to obtain the user ID and position.
Create a record
Actions: "Create record default action," "Validate record before creation for object-level checks."
You request to create a John Best contact whose email is j.best@gmail.com and who lives in New York. If Creatio.ai cannot find specialized agent and skill to create a contact record, Creatio.ai uses the universal fallback action to create a record, leading to execution of "Create record default action":
- Identify the target object ("Contact" (
Contactcode)). - Identify the structure of the target object ("Contact" columns).
- Map the input fields and validate data via the "Validate record before creation for object-level checks" action.
- If data is valid, execute the "Create record default action" action. Otherwise, ask the user to clarify input data.
- Return a confirmation and link to the created record.
Use actions in custom AI Skills
In general, your prompt has to provide all required data for the action to work, mention the action code explicitly, and specify what data to query to use an action in an AI Skill.
Search records
The search action requires keywords to work properly. As such, you can use the following prompt:
1. Generate Keywords: Use case details to generate up to 3 keywords for searching the knowledge base.
2. Search Knowledge Base: Use [SearchEntities] to search only the KnowledgeBase entity with the keywords.
Retrieve entity contextual data
The data retrieval action requires specific fields to be mentioned to work properly. As such, you can use the following prompt:
1. RetrieveEntityData the current page. You need to get the values of fields that may contain a contact or account ID.
Create record default action
"Create record default action" can be used in AI Skills that are designed to create a record in a specific scenario, where additional custom actions gather and analyze data before record creation. Such AI Skills can be implemented without the following:
- Writing prompt checks to mirror required fields or object-level business rules.
- Adding steps in the prompt that ask the user to confirm record creation.
- Using a specialized action to create a record in a particular object that serves as the target of the skill.
- Including a prompt instruction to return a link to the created record.
The skill has to focus on the logic specific to the business case and then simply instruct Creatio.ai to create the record using the collected values. As such, you can use the following prompt without explicitly referencing the "Create record default action":
Save the call script as a task.
In complex scenarios, we still recommend mapping values to the object columns in the skill prompt as it provides Creatio.ai with clearer guidance on how to process data.
SourceCode actions
These are code-based system actions implemented in C# for advanced or performance-critical tasks. They enable developers to define custom logic by inheriting from BaseExecutableCodeAction class. They offer direct execution outside the Process Engine for lower latency and deeper system access.
Limitations
Creatio.ai system actions have the following limitations:
- "File," "Image," "Image Link," "BLOB," "CRC," and "Color" type object columns are not supported.
- Page-level business rules are not supported. Move such logic to object level.
- It is not possible to interpret "Unique identifier" values without prompt guidance. For example, system actions cannot create new feed posts because the corresponding object has a "Unique identifier" column that contains a record ID that could be from different objects. This limitation does not apply to regular lookups.
- It is not possible to create records in system objects or in objects not returned as part of "Create record default action."
- It is not possible to search for lookup values missing from "SearchEntities" or "Get Lookups Value" actions.
- Creating collections or multiple interconnected records in one request is not supported. While this might work in some cases, increased request complexity can reduce accuracy.