Understanding Credits in Trigify
Trigify uses a credit-based system to keep things simple and flexible. Every time an action is executed — whether it's running a workflow node, enriching a contact, or posting content — credits are consumed.
Simple Usage Model: Your credits directly reflect usage — the more actions you run, the more credits are used. No hidden fees, no surprises.
Please Note: Credits are only used with ‘Social Listening’ and ‘Workflow’ features.
What is a Credit?
A credit is the unit of usage inside Trigify. Each action you perform consumes a set number of credits.
The number depends on the type of action — some are lightweight (like finding a social post), while others require more processing power (like enrichment or AI nodes).
How Credits Are Charged
Credits are deducted per execution. For example:
If your workflow finds 10 social posts, that will use 10 credits (1 per post).
If you enrich 5 emails, that will use 50 credits (10 per enrichment).
If a workflow includes an AI node, credits will vary depending on the size of the task.
Credit Costs by Action
Here's a breakdown of how credits are charged for different actions:
Action | Credit Cost |
Social Post (Listening) | 1 credit per post found |
Premium Integrations | 2 credits per action |
Email Enrichment | 15 credits per enrichment |
People / Company Enrichment | 10 credits per enrichment |
New Post | 1 credit per post |
AI Node | 1-7 Credits (depending on complexity) |
Tracking Your Credits
You can easily monitor your credit usage inside Trigify by the following ways.
Quick Look:
In the top right of your app, click the usage button

In-depth Usage:
Go to Settings → Credits Usage.
Here you'll see an exact breakdown of where credits are being used.
If you're on a Pay As You Go plan, you can control how much you spend by going to the manage plan page.
If you're on a monthly plan, this remaining credits you have left for is for the current 30-day cycle.

Example Scenarios
Scenario 1: Social Listening Workflow
You set up a workflow that tracks Reddit mentions of your brand. It finds 20 posts.
20 credits are used (1 per post).
Scenario 2: Sales Prospecting Workflow
You enrich 10 new leads with email and company data.
250 credits are used.
Scenario 3: AI Content Workflow
You run an AI node that generates a detailed campaign summary.
Between 3–5 credits are used, depending on complexity.
Pro Tip: Keep an eye on your credit usage in Settings to understand which workflows are consuming the most credits. This helps you optimize your automation and manage your budget effectively.
How to Save Credits
There are a few strategies to minimize your credit usage while maximizing platform functionality:
1. Use Your Own AI API Keys
Pro Tip: By adding your own API keys for AI models, you won't be charged any platform credits when using the AI agent node!
How to set it up:
Navigate to Settings (found in the bottom left menu)
Go to the AI Settings page
Upload your API key for your preferred provider
Select which model you want to use with your API key
Supported AI Providers:
Anthropic (e.g., Claude 4.5)
OpenAI
Gemini
More providers coming soon!
⚠️ Important: When using workflows, make sure to select the model you've configured with your own API key. If you select a different model, the platform will use its own credits instead.
Example: Using Your Own Anthropic API Key
Let's say you've added your Anthropic API key and configured it to use Claude 4.5:
When you select "4.5" in the workflow AI agent node, you'll see "Anthropic is configured"
This means you're using your own API key
No platform credits will be charged for this agent action
If you select “3.5” instead, you will use platform credits
HTTP Node & Custom API Integration
Zero-Credit External Integrations
One of the most powerful ways to extend platform functionality without spending credits is through HTTP nodes and custom API integrations.
What Are HTTP Nodes?
HTTP nodes allow you to make direct API requests to external services using your own API keys. The best part? They don't cost any platform credits.
💰 Cost Savings: When you add an HTTP node to your workflow, you'll notice there are no credit icons displayed. This means using your own API keys for HTTP requests is completely free of platform credit charges.