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 (e.g. each email attachment)

Examples

  • Send one email with 2 attachments:

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

  • Send 1 HTTP request with a document body and 1 email:

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

  • Send 2 emails with 1 attachment each, and 1 HTTP request:

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

Document generation caching

TemplateDocs automatically tries to avoid charging twice for identical document generations within the same workflow run by reusing cached results where possible.

Caching is applied automatically and on a best-effort basis. Because workflows can run steps in parallel, cache reuse is not guaranteed in all cases, and repeated generations may still be billed.

Next Steps

Credits - TemplateDocs Documentation