Monitoring & Credits

The Monitor section gives you visibility into everything running in your workspace: workflow executions, credit consumption, error rates, and system health.

Monitor dashboard

Access monitoring from the Monitor section in the left sidebar. The dashboard shows:

Execution overview

MetricDescription
Total executionsNumber of workflow runs in the selected time period
Success ratePercentage of executions that completed without errors
Failed executionsCount of executions that errored out
Average durationMean execution time across all workflows

Execution history

A chronological list of all workflow runs with:

ColumnDescription
WorkflowWhich workflow ran
StatusSuccess, Failed, or Running
Started atWhen the execution began
DurationHow long it took
TriggerWhat initiated the run (webhook, schedule, manual, etc.)
CreditsHow many credits this execution consumed

Click any execution to see the full step-by-step trace: which nodes ran, what data flowed between them, and where errors occurred (see Execution History).

Credit usage

Every workflow step uses 1 credit, and a few data-heavy steps (AI agents, search, scraping, SEO and enrichment) use more. Monitor credit usage in Monitor → Credit Usage.

Credit costs by category

CategoryNodeCredits each time it runs
All stepsFlow control, integrations, database, Send Email to Yourself1
AIAgent, Tiny Scout, Tiny Composer10
AITiny Search10
AITinyGPT, Tiny GPT Writer, Tiny GPT ResearcherAt least 1
ScrapingScrape Page, Extract Data, Map URLs2
ScrapingCrawl Site2 per page crawled
ScrapingWeb Search2 per result returned
VisionExtract Text, Read PDF, Extract Table, Extract Fields, Ask Document, ClassifyAt least 1
EnrichmentCompany Enrichment, Email Enrichment10
EnrichmentPerson Enrichment20

A step that errors still uses 1 credit. See Credits & Usage for SEO step prices and TinyTables costs.

Usage breakdown

The Credit Usage page shows:

  • Remaining and used: credits left and credits consumed
  • Forecast: how long your balance lasts at your current daily average
  • Usage by Product: which products used your credits
  • Daily Credit Consumption: credit usage over time
  • Recent Credit Activity: the latest credit charges

Managing credit costs

StrategyHow
Add early filtersPut If-Else nodes before AI nodes to skip processing for irrelevant data
Cache resultsStore AI results in a database. Check cache before calling AI again for the same input.
Batch wiselyA For Each loop with 100 items and a Person Enrichment node uses about 2,000 credits (20 x 100), plus 1 credit per other step in each iteration
Use the right nodeCompany Enrichment (10 credits) is cheaper than Person Enrichment (20 credits). Only look up people when you need person-level data.
Test with samplesDuring development, limit batch sizes to 5-10 items

Error monitoring

Error types

Error typeCauseResolution
Connection errorIntegration auth expired or API is downRe-authorize in Build → App Authorizations
Rate limitToo many API calls to an external serviceAdd Delay nodes between requests
TimeoutA node took too long to respondCheck the external service; consider retries
Validation errorInput data doesn't match expected formatAdd data validation before the failing node
Credit exhaustionOut of creditsUpgrade plan or wait for next billing cycle

Setting up error alerts

You can add error handling to any workflow to get notified when things go wrong:

Any node → Error branch → Send Email to Yourself (HIGH priority) + Slack (#alerts)

See Error Handling for details on configuring error branches and retry logic.

Workflow health indicators

On the main Workflows list, each workflow shows health indicators:

IndicatorMeaning
Green dotAll recent executions succeeded
Yellow dotSome recent executions failed (intermittent issues)
Red dotMost recent executions are failing
Gray dotWorkflow is paused or hasn't run recently
Tip

Set up a "meta-workflow" that runs daily, checks your credit balance via the Monitor, and sends you a Slack alert when credits drop below 20% of your monthly allowance.

Warning

Credit-consuming nodes still cost credits during test runs. Use the Test tab on individual nodes during development to avoid running the full workflow repeatedly.