# Count daily operations records

Use a scheduled database aggregate to prepare a count for a later dashboard or notification step.

## Plan availability

| Feature | Free | Starter | Pro | Enterprise |
| --- | --- | --- | --- | --- |
| Databases | Not included | 1 | 2 | Unlimited |
| Active workflows | 3 | 10 | 45 | Unlimited |

Allowances follow the [published Chatigram pricing page](https://chatigram.com/pricing/). Your organization’s Billing & Plans screen confirms its subscription and current usage. Plans can change. Plan information reviewed 2026-11-10.


## The business outcome

Use a scheduled database aggregate to prepare a count for a later dashboard or notification step.

This is an importable starter using Chatigram’s current native nodes. It needs destination-specific setup; it does not imply a dedicated connector for every CRM or ERP brand. Check your software’s API documentation and permissions.

## Before you begin

Select the database/table, add the filters that define your reporting period, and review the schedule. Choose any downstream delivery step separately.

The reserved example.invalid endpoint is deliberately non-working. No real customer data, account credentials, or private resource identifiers are embedded. Keep the workflow disabled until setup is complete.

## Configure the workflow

1. Open countRecords and select the table you intend to summarize.
2. Keep COUNT to count matching rows, or select a supported numeric aggregation and column if you need a sum or average instead.
3. Configure the filters for the reporting period. An empty filter list counts all matching table rows, not automatically today’s records.
4. Use total in a reviewed report or message step. The supplied graph prepares the value and handles failure without sending anything.

## Test the outcomes

- Compare the result with a small known set of test records.
- Check the distinction between zero matching records and an aggregation error.
- Verify period boundaries and timezone choices.

Open [Workflow Activity](/workflows/activity/) after the test. Import validation checks the definition; it does not prove a remote API accepted the business operation. Check the destination before repeating a send or write.

## Make it your own

Put reusable public settings in [Properties](/workflows/properties/), configure credentials through the protected connection options, and keep explicit error paths. Explore [App Connections](/integrations/overview/) for existing provider-specific actions you can substitute through the editor.

Use the copy controls below for the complete workflow or its first node. The diagram and downloads come from the same definition. Use Share recipe to share the guide’s public address.


## Copyable workflow

https://docs.chatigram.com/examples/daily-operations-total.json