Execution credits
Each run consumes credits based on the nodes it executes.
TameAutomation plans include a credit budget. Each workflow node consumes a defined number of credits, so you can estimate monthly operational volume without relying only on a raw node count.
Credit catalog
Available nodes have a declared execution cost.
The initial catalog uses a simple metric: 1 credit for each executed node. If more advanced nodes are added, their credit usage will be stated clearly before use.
| Node | Type | Credits | What it covers |
|---|---|---|---|
| IMAP | Email input | 1 | Reading or fetching messages from an IMAP mailbox during a run. |
| SMTP | Email output | 1 | Sending transactional emails or playbook-generated replies. |
| Telegram | Messaging | 1 | Sending or handling Telegram messages inside an operational workflow. |
| Claude | AI model | 1 | Calling Claude through a customer-provided API key in BYOK mode. |
| OpenAI compatible | AI model | 1 | Calling customer-connected OpenAI-compatible endpoints. |
Quick example
If a run executes IMAP, Claude, Telegram, and SMTP, it currently consumes 4 credits: 1 credit for each executed node.
Back to plans