How features use credits

understand the credit cost of your activities in make with an overview of how different features in make—apps, modules, and in app features—consume credits the next sections explain credit usage by features and by operations in modules credits by feature this chart breaks down make's credit usage logic for all features, including apps and in app features, depending on whether you use credits docid\ hh nrtakeqakbmg63uuin or your own connection (e g , an api key) to an external provider, if relevant feature uses make's ai provider uses your connection make ai tools docid\ qziwfqxhlmorepv5b4uqw (app) dynamic 1 credit per operation + credits based on token usage fixed 1 credit per operation make ai agents docid 0kbnuoduk1emvkqnwmdqc (app) dynamic 1 credit per operation/chat + credits based on token usage fixed 1 credit per operation ai prompt (in app feature) dynamic credits based on token usage no additional cost make ai content extractor docid\ uhne eytqewkdesstyyjo (app) fixed (1 credit per operation) or dynamic (credits based on token, file, or page based usage), make ai content extractor docid\ uhne eytqewkdesstyyjo n/a all other features fixed 1 credit per operation n/a as mentioned above, all other features consume credits based on a fixed rate of 1 credit per operation the next section details the relationship between credits and operations for each module type credits by module type most non ai apps at make consume credits on a credits docid\ hh nrtakeqakbmg63uuin basis based on operations in modules there are several types of modules docid\ bkdeyubelio6yvvcosrxj at make, each using credits differently based on their place in the scenario and how they process data trigger modules use 1 credit per run, regardless of whether they return data even when a trigger finds no new data, it still uses 1 credit for checking for example, in the google sheets > watch new rows module below, the scenario run retrieved no new data, but used 1 credit for the operation search modules use 1 credit per run, even when they return multiple bundles for example, the google sheets > search row module below runs once to search rows according to the specified criteria it only uses 1 credit for this operation despite returning 10 rows, or bundles action modules (those with "add," "update," "delete," etc) use as many credits as runs needed to process all bundles it uses 1 credit per input bundle processed for example, the google sheets > search row module below returned 10 rows and used 1 credit the following delete rows module must run 10 times to delete each of the 10 rows, using 10 credits the scenario uses 11 credits total aggregator modules combine multiple bundles into a single bundle, called an array aggregators use 1 credit for each aggregation for example, the array aggregator below combined 10 contacts, or bundles, from the google sheets > watch new rows module into an array this aggregation used 1 credit iterator modules split an array into multiple bundles iterators use 1 credit to return an array, and the following modules use 1 credit for each iterated bundle for example, the iterator below received an email with 5 attachments and split them into 5 separate attachments, or bundles it used 1 credit to split the attachment array, and the google drive > upload a file module used 5 credits to upload each attachment these module types do not use credits error handlers modules rollback, break, resume, commit, ignore router modules and filtering scenarios docid\ f8fhrvoqwck48nx fjryf overall, the same fixed credit usage logic applies to all modules, except triggers when a module returns multiple bundles, each bundle triggers its own run in each module it passes through this happens because make processes bundles separately each bundle's scenario run is an operation, and each operation uses a predetermined number of credits – usually 1 for example, a trigger module returns 10 new contacts, and the next module runs 10 times, once for each contact, to add them to a table adding 10 contacts results in 10 operations, using 10 credits you can learn more about bundles and their relationship to operations in operations docid\ zr2rwmilmj 19r85mlawm