Skip to main content

Node execution and credit usage

Learn how credits are used by node executions through sample workflows.


» Visit Pricing page to learn more about different plans and their details.

Node types, executions and credits

Credits are the currency that equate to execution of a single node. The following table illustrates how credits are consumed based on different node types in Actioner.

TypeCredit it usesNotes
Action node1 credit per executionAn action node consumes 1 credit when executed.
Operator node1 credit per executionEach operator node uses 1 credit when executed.
Note: How many times a loop is executed is calculated through the number items in that loop.
Function node1 credit per executionA function node uses 1 credit when executed.
Output node1 credit per executionAn output node uses 1 credit when executed.
Job node1 credit per executionA job node uses 1 credit when executed.
Response node1 credit per executionA response node uses 1 credit when executed.
Workflow node1 credit per executionA workflow node uses 1 credit when executed.
AI node- 1 credit per execution
- 1 credit per every 100 words*
Each AI node uses 1 credit when executed. Additionally, 100 words* generated by OpenAI consumes 1 credit.
*In the context of Actioner AI nodes, a word refers to a unit used for natural language processing. Specifically, for English text, 1 word is approximately equivalent to 5 characters. This measurement helps determine the usage of AI nodes. As a point of reference, the collected works of Shakespeare are about 900,000 words.

Example workflows

Below you can find example workflows to help you understand credit usage of various nodes.

Example 1: Simple workflow

Summary: Capture new contacts from HubSpot and send a notification to #new-leads channel.

Example 1: Simple workflow

Node typeAlias and nameHow it worksCredit usage
Triggerevent
New contact created
Contact created
Integration: HubSpot
None
Actionaction0
Send message to #new-leads
Send message to channel
Integration: Slack
1 credit per execution

When a new contact is created in HubSpot, this workflow executes 1 node (action0 x 1), resulting in the consumption of 1 credit.

Example 2: Discarded event

We’ll be extending the Example 1, this time to notify #new-leads channel only if the lifecycle stage is “Lead”.

Summary: Retrieve new contacts from HubSpot and notify #new-leads channel if the contact’s lifecycle stage is “Lead”.

Discarded events

If the event is discarded because the Trigger condition is not met, it will not result in any credit consumption since no nodes are executed.

Example 2: Discarded event

Node typeAlias and nameHow it worksCredit usage
Triggerevent
New contact created
Contact created
Integration: HubSpot
Trigger condition enabled
None
Actionaction0
Send message to #new-leads
Send message to channel
Integration: Slack
1 credit per execution

In the event of a new contact in HubSpot, if the contact's lifecycle stage is “Lead”, this workflow will execute 1 node (action0 x 1), and consume 1 credit.

However, if the contact is not a “Lead”, the event will be discarded, resulting in no node execution and, consequently, no credit consumption.

Example 3: Workflow with a condition operator

Summary: Monitor new Zendesk tickets, check ticket details, and notify #urgent-requests channel if the ticket priority is “Urgent”.

Condition operators

When a workflow contains a condition, only the nodes within the matching condition's path are executed, altering the node execution consumption based on the conditions met.

Example 3: Workflow with a condition operator

Node typeAlias and nameHow it worksCredit usage
Triggerevent
New ticket
Ticket created
Integration: Zendesk
None
Actionaction0
Get ticket
Get ticket
Integration: Zendesk
1 credit per execution
Actioncondition0
Is it an urgent ticket?
Checks if priority in action0’s response equals to urgent1 credit per execution
Actionaction1
Notify #urgent-requests channel
Send message to channel
Integration: Slack
1 credit per execution

When there is a new Zendesk ticket; if the request’s priority is “Urgent”, this workflow will execute 3 nodes (action0 x 1 + condition0 x 1 + action1 x 1), and consume 3 credits.

However, if the priority is not “Urgent”, workflow will execute only 2 nodes (action0 x 1 + condition0 x 1), and consume 2 credits.

Example 4: Workflow with a loop operator

Summary: Send direct message to members in #nyc-office channel asking everyone to complete a survey to collect feedback on employee well-being during remote work. This will require looping through members in the channel and sending them separate messages.

Loop operators

Node execution of a loop is calculated through the number items and the executed nodes inside that loop.

Example 4: Workflow with a loop operator

Node typeAlias and nameHow it worksCredit usage
ManualManualForm with no inputsNone
Actionaction0
List users in #nyc-office channel
List users
Integration: Slack
1 credit per execution
Actionloop0
Loop through channel members
Loops through each item in the response of action01 credit per execution
Actionaction1
Send DM
Send direct message
Integration: Slack
1 credit per execution

If the number of members in the Slack channel is 5, the total number of nodes executed in this workflow will be 7. (action0 x 1 + loop0 x 1 + action1 x 5), resulting in the consumption of 7 credits.