🟡 Credit System

In Monkedo, the credit system governs the usage of the automation tool. As users run automations, their credit balance decreases based on the actions and operations performed.

Credits are consumed each time a component runs. In the system, components are categorized as either paid or free. Paid components consume 1 credit per execution, while free components do not consume any credits (with exceptions in cases of abuse and errors). Paid components are listed separately, and free components are clearly marked with a Free tag.

Some components are classified as basic and are available for free use. However, there is a usage limit for these free components: for every 100 executions, 1 credit will be deducted randomly.

In Monkedo, all app components consume 1 credit each time they are executed. This applies universally to app components, regardless of the operation's outcome or the specific task being performed.

Attention: Some other no-code tools, such as Zapier and Make, require additional credits for certain apps. In Monkedo, all app components are 1 credit.

You can utilize the freemium plan of Monkedo with up to 1,00 credits per day. Once this limit is reached, automations will be paused until the following day, as the limit is renewed daily.

If the freemium plan does not meet the your needs, you have the option to upgrade to a more suitable plan. Upon activation of a new plan, you can use the allocated credits either individually or distribute them among your team members. It's important to note that the total number of credits available does not increase as more users are added to the team. The credit allocation remains fixed based on the chosen plan, regardless of team size.

The daily credit for paid plans can be changed by the users.

Credits are deducted each time a component is executed. To grasp how this works, review the provided examples, which are simplified for ease of understanding. In more complex automations, where iterative components or tree-like flows are used, the number of component executions can increase significantly. Or, if a component's output triggers another component to run multiple times, the total number of executions can rise. This increased activity results in higher credit consumption.

Example 1:

• Automation Components:

  • 1 free trigger component

  • 3 app action components

  • 1 free data action component

• Schedule:

  • Runs every Monday at 10:00 AM and 6:00 PM

• Credit Calculation:

  • The automation runs twice a day, totaling 2 runs per day.

  • In a week, the automation runs 2 times (once at each scheduled time on Monday).

  • Credits for app components: Each run uses 3 app action components. So, for 2 runs, the total is 3 components x 2 runs = 6 app component uses, which equals 6 credits.

  • Total credits used in a month: 6 credits for a week. 4 weeks x 6 credits = 24 credits.

Example 2:

• Automation Components:

  • 1 email trigger component

  • 1 app action component

  • 1 free action component

• Schedule:

  • Runs every 24 hours

• Credit Calculation:

  • The automation runs once every 24 hours, totaling 1 run per day.

  • In 24 hours, it uses 2 credits (1 credit for the email trigger component and 1 credit for the app action component).

  • Monthly credits used: 30 days x 2 credits per day = 60 credits.

Example 3:

• Automation Components:

  • 1 free trigger component

  • 1 free iterate table component with 100 rows

  • 1 app action component

• Schedule:

  • Runs once

• Credit Calculation:

  • Credits for the app action component: 1 credit (since it runs once).

  • Credits for the free iterate table component: It runs 100 times for 100 rows, which equals 1 credit (as every 100 executions of free components result in 1 credit deduction)

  • Total credits used: 1 credit (for the app component) + 1 credit (for 100 free iterations)= 2 credits.

Q: Do I consume credits when creating automations in the editor?

A: No. Running components while creating or editing an automation in the editor does not consume credits. You can freely test your automations before deploying them.

Q: What happens to my credits if the automation fails after deployment?

A: Components can fail due to incorrect configuration or invalid data provided. Even if an error occurs, the system will still run the component, so faulty operations will consume credit. But if the error occurs repeatedly, the automation stops, and no further credits are consumed.

Q: What happens if my credits run out while an automation is running?

A: It will finish the current component run, save the current state of the automation, and resume when you renew your credits or when they are automatically renewed at midnight (if the daily credits have run out).

Q: Let's say my monthly credits run out and they will be renewed in one week. What will happen to my automations in the meantime? When my credits are renewed in one week, will the automations that did not run in the past week execute?

A: During this period, we pause your automations, which means the triggers stop controlling events. As a result, no automations will run or create records while your credits are depleted. When your credits are renewed in one week, the automations that were paused will not retroactively execute.