Credits

Credits are used to measure and bill workflow run usage in a simple, predictable way. Each run has a small base cost, plus additional credits for any extra tasks it performs.

Cost model

Every workflow run follows the same pricing rules:

  • 1 credit to invoke a workflow.
  • The first 3 task credits are included in that base cost.
  • Each additional task after the first 3 adds 1 credit to the final run cost.

This means that most small workflows cost just 1 credit, even if they include a few actions.

Task credit table

Task credits are counted per workflow run, based on which steps were executed (and what they do):

TaskCostNotes
HTTP request1 creditPer request
Send email1 creditPer email sent
Document generation1 creditPer generated document
Upload file to Google Drive1 creditPer file uploaded
Send document to Zapier1 creditPer document sent
Send document to Make1 creditPer document sent

Examples

  • Generate a document, send it by email and upload it to Google Drive:

    • Run invocation cost = 1
    • Task credits = 1 (document generation) + 1 (send email) + 1 (upload to Google Drive) = 3
    • Included in base cost = 3
    • Final cost = 1 (1 + 3 - 3 = 1)

  • Generate a document, send it by email and send it via HTTP:

    • Run invocation cost = 1
    • Task credits = 1 (document generation) + 1 (send email) + 1 (HTTP request) = 3
    • Included in base cost = 3
    • Final cost = 1 (1 + 3 - 3 = 1)

  • Generate 2 documents, send each to a different recipient by email and upload both to Google Drive:

    • Run invocation cost = 1
    • Task credits = 2 (document generation) + 2 (send email) + 2 (upload to Google Drive) = 6
    • Included in base cost = 3
    • Final cost = 4 (1 + 6 - 3 = 4)

Next Steps

Credits - TemplateDocs Documentation