Pricing in altaFlow is based on the usage, which is measured by the number of actions performed by the workflow.
Each time a bot is triggered and completes its task, it consumes one credit. Additionally, every workflow execution is counted as a paid credit. However, regardless of how many completed documents there may be, each workflow execution is counted only once toward the total number of credits. This means that even if a document is filled out by multiple signers, you will only be charged for a single action when it is executed.
Note:Each time a workflow runs, it uses one credit. If a workflow is initiated from a start link, it only uses a credit after the the first step is completed. This is because public links can be accessed by unauthorized individuals, which may lead to an overstatement of usage.
The number of credits available for bots depends on your specific plan. If you exceed the included credits in your plan, you will be charged an extra fee of $0.50 per additional action used at the end of the month. To learn more about altaFlow plans, check this article .
Free and paid bots are clearly marked in the bot list, making it easy to differentiate between them. The list of the bots can be found in this article.
To avoid extra charges, it is recommended to consider upgrading your plan if you consistently require more credits than what is provided. It's worth mentioning that purchasing additional credits is not an available option.
Let’s check the credit usage in the example.
Let's say you have an HR process in which job candidates submit their resumes through an airSlate workflow. You want to export the data from the resumes to a Google Sheets spreadsheet and save the resumes themselves to a Google Drive folder.
In the airSlate workflow, create a form that includes fields for the candidate's name, contact information, and resume file upload. You can also include other fields as needed, such as the position they are applying for or their availability.
Add the Export to Google Sheets bot to the workflow. Configure the bot to export the data from the form to a specific Google Sheets spreadsheet. You can choose which fields to export and how they should be formatted in the spreadsheet.
Add the Save to Google Drive bot to the workflow. Configure the bot to save the uploaded resume files to a specific Google Drive folder. You can choose how the files should be named and organized in the folder.
Once the bots are set up, whenever a candidate submits a resume through the workflow, their information will be exported to the Google Sheets spreadsheet and their resume file will be saved to the Google Drive folder.
In the provided example, let's break down the actions and their corresponding credits:
Workflow execution: this action uses one credit. It represents the start of the workflow.
Export to Google Sheets bot: this bot is triggered when a candidate submits a resume. Each time this bot is completed, it uses one credit. It exports the candidate's information to the Google Sheets spreadsheet.
Save to Google Drive bot: this bot is also triggered when a candidate submits a resume. Each time this bot is completed, it uses one credit. It saves the candidate's resume file to the Google Drive folder.
Therefore, for each candidate who submits a resume through the workflow it will consume three credits: one credit for the workflow execution and one credit for each of the two bots.
Remember, this example is specific to the scenario described, and the number of credits may vary depending on the complexity and configuration of your own workflows.