Usage and credits
Runs, data and credits this month, how credits are counted, and what happens at the allowance.
The Hub measures its work in credits. Every workspace has 10,000 credits a month. The Usage page shows how many runs, how much data and how many credits your connections have used so far this month. Everyone in the workspace can read it.
The Integration Hub is in English only, so its labels are quoted in English in the Danish articles too.
How credits are counted
| What | Credits |
|---|---|
| A finished run, successful or failed | 1 per run |
| Data the run fetched | 5 per MB |
| Records created or updated | Free |
| A mailbox check that finds no new mail | No run fee (any data it fetched still counts) |
| Platform rows that Juvaro runs, such as directory sync | Not charged |
| The Webmercs vendor connection | Not charged |
Data is counted to the fraction of a megabyte, so credit figures have one decimal. A single fetch reads at most 5 MB. Anything beyond that is not fetched in that run, and the connection's row is marked Truncated.
A worked example for Your Company in one 30-day month:
- The Intune import runs daily and fetches about 2 MB each time: 30 runs × (1 + 10) = 330 credits.
- The support mailbox is checked every 5 minutes. Most of the 8,640 checks find nothing and cost nothing. 1,200 checks find mail and pay the run fee, and the mail adds up to 40 MB: 1,200 + 200 = 1,400 credits.
- Total: 1,730 of the 10,000 credits.
That is why a mailbox can be checked every minute without using up the allowance. See How often a mailbox is checked.
The Usage page
Open Usage in the left rail. The header shows the current month and "Runs, data ingested, and credits used this month."
Five figures sit at the top: Runs, Success rate, Records, Data ingested and Credits, shown as used out of 10000 with a bar. The bar turns red when the workspace is over its allowance.
The table below has one row per connection that has run this month: Connector, Runs, Records, Data, Credits and Status. Click a column header to sort. The status column shows:
- Truncated: a fetch hit the 5 MB cap, so some data was not read. Narrow the source (for example a filter on the REST endpoint) or run it more often so each fetch is smaller.
- Not charged: work Juvaro runs for you, such as directory sync. It is shown so you can see it happening, and its credits column has a dash.
A connection with no runs this month is not in the table. Early in the month the page may say No usage yet: "Runs this month will appear here."
The month in the header follows your browser's language. In a Danish browser it may read "oktober 2026" even though the rest of the Hub is in English.
The page always shows the current month. There is no period picker for earlier months and no export.
Other places that show credits
- The Connections page has the figure Credits used, shown as used out of 10,000.
- Each connection's page has Credits this month for that connection alone, with the rate "1 credit/run (+5/MB)". See A connection's page: figures, Pause and Resume.
When the allowance is used up
When the month's credits reach 10,000, the Usage page shows the red banner "Over your monthly credit allowance - scheduled runs are paused and Run-now is blocked until next month."
- Scheduled runs stop, for every connection, including shared mailboxes. New mail is not turned into tickets until runs start again.
- Run now is refused with "429 - Monthly credit allowance exhausted - resumes next month or raise the allowance".
- Runs start again by themselves on the 1st of the next month. The month follows UTC, so in Denmark it turns at 01.00 or 02.00 at night.
- The Hub has no setting for the allowance.
If the credits climb faster than you expect, sort the table by Credits. The usual cause is a connection that fetches a lot of data on a tight schedule. Running it less often, or fetching less each time, brings the figure down.