Any read/write/fetch operation related to a config object

Create new data objects (leads, contacts, cases...) or updating existing data objects via user action and API. Rates are measured based on the number of create and update operations are run on the platform.

Fetch a list of data, based on certain filters on both indexed and non-indexed attributes. For example a user fetching a list of leads from the process list UI. List operations are data intensive and it is advised to run fetch operations on indexed attributes to ensure runtime is within the threshold. See threshold details here.

Fetching a single data object is typically used when a user agent clicks on the process for its details, or fetches data through process fetch API.

Search is one of the most common use cases across web and mobile applications. Rates are measured as number of searches done by your user agents. Runtime and size thresholds are critical in search operations since the database size is a critical element in the speed of search executions.

Real-time sync of data to clients like webapp, mobile app is imperative for your users to have latest up-to-date data before they begin their scheduled workflows. Syncs happen every time there is a data update detected by the ChakraHQ platform.

Pushing data to a data stream

Create or update a media data object like a photo or a video

Fetch a media object like a document

List log entries for a certain log type

historyListOp is used every time an agent accesses a process history on the UI or is accessed through the ChakraHQ history API. Pay for the number of times you use the history listing option even though history is captured for all processes. Runtime and size thresholds apply here and are key to usage.

Represents a single chart query operation. For example If your chart has 10 granular metrics - loading the chart will constitute as 10 chartQueryops

Capture of geolocation of the on-field user. For example, collecting geolocation to ensure field agent was at customer's address. Setting the frequency of the capture here will determine the size dimension of the geolocationListOp usage.

Fetching a list of geolocations captured for an agent. For example, listing the coordinates captured for an agent to map their route for the day. Rates apply based on the number of times the listing feature is actually used.

Load a google map for location selection / viewing

Show predictions for google maps location search

Reverse geocode a selection location to get location name and details

Fetch location details for a selected google location

list notifications for a single client

Optimize the use of the derivedAttributeCompute by controlling the number of executions. Efficiency improvements on the data ops will automatically result in better usage of the derivedAttribute usage. Runtime thresholds are critical for high-input derivedAttributes. See ore about the thresholds here.

Script executions depend on your configuration. For example, if the aforesaid prioritization example is set for every new lead, then estimated number of script executions will be as many as the number of leads created.

Lifecycle rules are an automation feature that are event based automations. Their usage is determined by the funnel progress through your process. Usage is counted based on the number of actions taken through lifecycle rules run over a period of time. Combine with external API’s, dataCreateUpdateOp and notifications, for maximum automation

API calls made outside the ChakraHQ platform. For example, update your internal systems with data every time a new sale is recorded. Pay for the number of API calls made through our externalApi configuration. Runtime and size thresholds apply.

ChakraHQ Platform can cache data fetched from external api’s and therefore let you boost speed as well as reduce the cost of the operations.

Allocator usage is measured on the number of times a successful allocation happens. For example, there’s 453 new leads been allocated to your agent team today. Therefore, your allocator usage for today is 453. Limits and thresholds apply to the runtime of the allocation. This means execution unit rates apply every time the allocator is successfully executed within the runtime and size thresholds. Runtime rates apply pro-rata for thresholds exceeded.

Rates are computed on the number of times emails are sent on the platform

SMS can be used through the authentication flow as well as for sending communications to your customers. Please check the OTP section for mode details on the authentication flow. Rates are computed on the number of SMSs sent through the ChakraHQ platform

OTP usage is measured on the number of times OTP based verification and authentication is used by your organization. Size and runtime thresholds rates apply if and only if the corresponding thresholds are exceeded. Please note, the costs don’t include email and sms communications. Please refer to the SMS and Email configurations and their costs here.

Push data to an external kinesis stream

Transactioanal data are data that is created by business users liek processes records and tasks

Data that is logged as part of auditing of a certain feature

Data that is part of the security auditing framework

Create or update a plugin specific data object

List data via a plugin

Fetch a single data point through a plugin

Usage of the background job Processing is measured based on the number of entries processed through file upload or bulk APIs.

Load a google map for location selection / viewing

Show predictions for google maps location search

Reverse geocode a selection location to get location name and details

Fetch location details for a selected google location

Real-time sync of data to clients like webapp, mobile app

Create new process objects (leads, contacts, cases...) or updating existing process objects via user action and API. Rates are measured based on the number of create and update operations are run on the platform.

Fetch a list of process, based on certain filters on both indexed and non-indexed attributes. For example a user fetching a list of leads from the process list UI. List operations are process intensive and it is advised to run fetch operations on indexed attributes to ensure runtime is within the threshold. See threshold details here.

Fetching a single process object is typically used when a user agent clicks on the process for its details, or fetches process through process fetch API.

Create new record objects (customers, accounts, contacts...) or updating existing record objects via user action and API. Rates are measured based on the number of create and update operations are run on the platform.

Fetch a list of record, based on certain filters on both indexed and non-indexed attributes. For example a user fetching a list of leads from the record list UI. List operations are record intensive and it is advised to run fetch operations on indexed attributes to ensure runtime is within the threshold. See threshold details here.

Fetching a single record object is typically used when a user agent clicks on the record for its details, or fetches record through record fetch API.

Create new task objects (calls, meetings...) or updating existing task objects via user action and API. Rates are measured based on the number of create and update operations are run on the platform.

Fetch a list of task, based on certain filters on both indexed and non-indexed attributes. For example a user fetching a list of leads from the task list UI. List operations are task intensive and it is advised to run fetch operations on indexed attributes to ensure runtime is within the threshold. See threshold details here.

Fetching a single task object is typically used when a user agent clicks on the task for its details, or fetches task through task fetch API.

Create new call objects or updating existing call objects via user action and API. Rates are measured based on the number of create and update operations are run on the platform.

Fetch a list of call, based on certain filters on both indexed and non-indexed attributes. For example a user fetching a list of leads from the call list UI. List operations are call intensive and it is advised to run fetch operations on indexed attributes to ensure runtime is within the threshold. See threshold details here.

Fetching a single call object is typically used when a user agent clicks on the call for its details, or fetches call through call fetch API.