Credit Allocation
Workflows use your workspace credits, allocated based on your plan and your number of users:Included credits are generous for standard automations: one credit covers about 10,000 standard workflow steps. Most teams won’t exceed this limit with typical workflow usage. Additional credits are primarily needed for advanced Code actions and AI-powered workflows. See Credits for rollover and credit packs.
How Credit Consumption Works
Credits are consumed when workflows execute, not when you create them. Each workflow action consumes credits based on its complexity:Credit Consumption by Action Type
-
Basic internal operations: Very low credit consumption
- Search Records
- Create Record
- Update Record
- Delete Record
- Form actions
-
Complex operations: Higher credit consumption
- Code actions (JavaScript execution)
- HTTP Requests to external services
-
AI features: Higher credit consumption
- AI Agent actions consume credits based on the AI model used
- More complex prompts and longer outputs use more credits
-
Delay actions: Minimal credit consumption
- The Delay node consumes 0.0001 credit ($0.0001) when it executes, the same as a standard workflow step
- No credits are consumed during the wait period
- A 5-minute delay costs the same as a 5-day delay
Real-Time Deduction
Credits are deducted in real-time as workflows execute. This means:- Draft workflows don’t consume credits
- Only active, running workflows use your credit allocation
- Failed workflows still consume credits for completed steps
Managing Credits
Check Credit Usage
- Go to Settings → Billing
- View your current credit consumption and remaining balance
- Monitor usage patterns to optimize your workflows
Purchasing Additional Credits
If you need more credits beyond your plan allocation:- Go to Settings → Billing
- Click on the option to purchase additional credits. Packages of different sizes are available.
- Credits are added to your current balance
Best Practices
- Batch Processing: Use bulk operations and Iterator actions efficiently to reduce individual action calls
- Manual Trigger Optimization: For manual triggers, choose
Bulkavailability to process multiple records in a single workflow run - Optimize Code actions for efficiency