Managing Credits

Understand and manage your workflow execution credits.

Overview

Credits are the unit of consumption in Spojit. Every workflow run debits credits from your workspace's allowance, and your plan determines the monthly allowance and the price of top-ups. Credits reset at the start of each billing period; top-up credits roll over for the duration of the plan.

Different node types cost different amounts. AI-heavy steps (LLM calls in Connector Agent mode, Transform structured mode, Knowledge queries) cost more than direct connector calls, scheduling, or data shaping. Workflow design choices, not just run frequency, drive your bill.

Before You Start

  • You must be a workspace admin to buy top-ups or change plan.
  • Any workspace member can view their own runs in Executions and see what they consumed.

Checking Your Balance

  1. Open Settings -> Billing.
  2. The Usage this period card shows credits consumed, credits remaining, and the date the allowance resets.
  3. Click View breakdown to see consumption per workflow and per node type for the current period.

What Consumes Credits

  • Connector calls - Cost per call. Direct mode calls cost the call itself; Agent mode also pays for the LLM round trip.
  • LLM steps - Transform structured mode, Knowledge nodes, Connector Agent mode. Cost scales with the model's input and output tokens.
  • Knowledge queries - Vector search plus the LLM that summarises the result.
  • Other nodes - Condition, Loop, Parallel, Trigger, Response, and Variable steps have nominal cost.

Buying Top-Ups

  1. In Settings -> Billing, click Buy credits.
  2. Choose a top-up pack. Larger packs have a lower per-credit price.
  3. Confirm in the Stripe checkout. Credits land in the workspace within a minute and appear in the Usage card.

Tips

  • Use Direct mode on Connector nodes whenever the tool call is deterministic. Agent mode is only worth its cost when the LLM needs to choose between tools.
  • Pick a smaller model for routine Transform steps. Reserve the most expensive models for genuinely hard reasoning.
  • Set workflow notifications on credit-heavy workflows so you spot regressions in consumption quickly.

Common Pitfalls

  • Running out of credits pauses scheduled and webhook-triggered workflows. Top up or wait for renewal to resume.
  • Loop nodes multiply cost. A loop of 1000 items running a Connector Agent step is 1000 LLM calls.
  • Test runs consume credits too. Disable or scope down expensive workflows while iterating in the designer.

Related Articles

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.