# FRED Release Calendar: Upcoming CPI, Jobs and GDP Releases (`accountable_eel/fred-release-calendar-alerts`) Actor Upcoming and just-published US economic data release dates (CPI, jobs, GDP and every other FRED release) from the FRED API, with a monitoring mode that only returns and bills release dates you have not seen. Bring your own free FRED key. - **URL**: https://apify.com/accountable_eel/fred-release-calendar-alerts.md - **Developed by:** [Adriana Voss](https://apify.com/accountable_eel) (community) - **Categories:** Developer tools, Automation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $5.00 / 1,000 release date returneds This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## FRED Release Calendar: Upcoming CPI, Jobs and GDP Releases **Know which day CPI, the jobs report, GDP and every other US economic data release comes out, and get told when a new date appears or a release has just come out.** One row per release date, from the St. Louis Fed's FRED release calendar: release name, date, whether it is upcoming, today or already published, and how many days away it is. Turn on monitoring and run it daily to get only the release dates you have not seen before, charged per row and free on a quiet day. **Who uses it:** traders and analysts who schedule around data releases, newsletter and research teams that publish a weekly "what is coming" post, and automation builders who want a Slack, Sheets or n8n trigger on the day a number lands. **You bring your own free FRED key.** The calendar comes from the FRED API, which requires a key. Create a free FRED account (the key is shown instantly), paste it into the *Your FRED API key* field, and your requests run on your own key and your own FRED request limit. This actor never ships, stores or shares a key. Without a key a run still succeeds: every search comes back as one `NEEDS_KEY` row that says where to get the key, and nothing is charged. **What you get, and what you do not:** release dates only. FRED does not publish a clock time, a consensus forecast or the actual figure, so there is no "8:30 ET" or "expected 0.3%" column. Dates are US Eastern calendar dates and FRED itself notes that a published date is not always the moment the data appears on its website. ### How to use 1. **In the Apify Console.** Open the actor page and click **Start** — the `releases` field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found. 2. **Via the API.** Call it directly with a POST request — no Console needed once you have an API token: ```bash curl "https://api.apify.com/v2/acts/accountable_eel~fred-release-calendar-alerts/run-sync-get-dataset-items?token=" \ -X POST \ -H "Content-Type: application/json" \ -d '{"releases":["CPI","jobs","GDP"]}' ``` 3. **On a schedule.** Save this actor as an Apify **Task** with the input you want, then add a **Schedule** (hourly, daily, weekly) so it runs on its own — no server of your own required. ### Input ```json { "releases": [ "CPI", "jobs", "GDP" ] } ``` One per line: a short alias for the headline release (CPI, jobs, GDP, PPI, PCE, retail sales), a numeric FRED release ID (10 is Consumer Price Index, 50 is Employment Situation, 53 is Gross Domestic Product) or any part of a release name ("Gross Domestic Product by State"). Leave empty to get every release in the window. Accepted formats: CPI, jobs, GDP, 53, "Producer Price Index". Each line of *Releases to follow* is one search. An alias (`CPI`, `jobs`, `GDP`) picks the headline release only, so `CPI` does not also return "Research Consumer Price Index". A plain phrase matches any part of the release name, and a number matches a FRED release ID exactly. A release that matches two lines is returned once. The window is *Days back* (default 7) before today to *Days ahead* (default 14) after it. The first request of a run takes about 15 to 20 seconds because FRED answers the calendar slowly; the rest are instant. ### Output One row per release date. This is what a run with the key pasted in returns for `CPI`, `jobs` and `GDP` (from a real run on 2026-10-11, trimmed to three rows): ```json {"query": "CPI", "found": true, "status": "OK", "source": "FRED API fred/releases/dates", "releaseId": 10, "releaseName": "Consumer Price Index", "releaseDate": "2026-10-14", "releaseStatus": "UPCOMING", "daysUntil": 3, "lastUpdated": "2026-09-11T15:51:26.000Z", "releaseUrl": "https://fred.stlouisfed.org/release?rid=10", "isNew": null, "firstSeenAt": null} {"query": "jobs", "found": true, "status": "OK", "source": "FRED API fred/releases/dates", "releaseId": 50, "releaseName": "Employment Situation", "releaseDate": "2026-10-02", "releaseStatus": "PUBLISHED", "daysUntil": -9, "lastUpdated": "2026-10-02T15:21:39.000Z", "releaseUrl": "https://fred.stlouisfed.org/release?rid=50", "isNew": null, "firstSeenAt": null} {"query": "GDP", "found": true, "status": "OK", "source": "FRED API fred/releases/dates", "releaseId": 53, "releaseName": "Gross Domestic Product", "releaseDate": "2026-10-29", "releaseStatus": "UPCOMING", "daysUntil": 18, "lastUpdated": "2026-10-01T15:09:22.000Z", "releaseUrl": "https://fred.stlouisfed.org/release?rid=53", "isNew": null, "firstSeenAt": null} ``` Every row carries `scrapedAt` and a `source` naming the route. `lastUpdated` is FRED's own "data last updated" stamp for that release and is `null` when FRED does not send one. With monitoring on, `isNew` and `firstSeenAt` are filled and `monitorStatus` says `NEW_RELEASES` or `NO_NEW_RELEASES`. Without a key, each search is one free row like this: ```json {"query": "CPI", "found": false, "status": "NEEDS_KEY", "message": "No FRED API key was supplied, so nothing was fetched for this search. Get a free key in about a minute ... and paste it into the \"Your FRED API key\" field. The key and its request limit are yours.", "scrapedAt": "2026-10-11T22:26:24.689Z"} ``` | query | found | status | searchSummary | releaseCount | truncated | monitorStatus | releaseDates | source | releaseId | releaseName | releaseDate | releaseStatus | daysUntil | lastUpdated | releaseUrl | isNew | firstSeenAt | scrapedAt | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | CPI | true | OK | | | | | \ | | | | | | | | | \ | | 1970-01-01T00:00:00.000Z | A miss (no key, a wrong key, or a search that matched no release in the window) comes back as a row with `"found": false` and a plain-English `message`, and is never charged. A rejected key is `INVALID_KEY`, a hit request limit is `BLOCKED`. ### Pricing Pay-per-event. A flat per-run fee covers session/proxy warmup; you're billed per item only when data is actually found and returned — see `.actor/pay_per_event.json` for exact prices. A miss is never charged. You are billed one *release returned* event per release date row. A search with no match, a `NEEDS_KEY` or `INVALID_KEY` row, and a monitoring run with nothing new are never charged. The FRED API key and its request limit are yours, not ours. ### Example runs Paste any of these into the Input tab and press Start. None of them contains a key: add your own in the *Your FRED API key* field to get release dates; leave it empty and each search returns one free `NEEDS_KEY` row that shows the shape. **The three headline releases, a week back and two weeks ahead.** The default. ```json { "releases": ["CPI", "jobs", "GDP"] } ``` **Everything scheduled in the next 30 days, upcoming only.** An empty list means every release. ```json { "releases": [], "daysBack": 0, "daysAhead": 30 } ``` **A daily release alert.** Run it on a daily schedule; each run returns only release dates you have not been given, including a release that has just moved from upcoming to published. ```json { "releases": ["CPI", "jobs", "GDP", "PPI", "retail sales"], "daysBack": 3, "daysAhead": 30, "onlyNewSinceLastRun": true, "deltaName": "macro-calendar" } ``` ### Terms and notice This product uses the FRED® API but is not endorsed or certified by the Federal Reserve Bank of St. Louis. By using this actor you agree to be bound by the FRED® API Terms of Use (fred.stlouisfed.org/docs/api/terms_of_use.html). Your key is yours and your use of it must follow those terms. This actor returns release dates only, not data series; series data can carry third-party copyright. FRED applies request limits per key, so a very large schedule can hit your own limit (the actor then reports `BLOCKED` and charges nothing). ### Use it from Clay, n8n, Make, or an AI agent This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token. ```bash curl "https://api.apify.com/v2/acts/accountable_eel~fred-release-calendar-alerts/run-sync-get-dataset-items?token=" \ -X POST \ -H "Content-Type: application/json" \ -d '{"releases":["CPI","jobs","GDP"]}' ``` **n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~fred-release-calendar-alerts/run-sync-get-dataset-items?token=`, Body Content Type `JSON`, JSON Body `{"releases":["CPI","jobs","GDP"]}` (swap in an expression from an earlier node for a real value). **Clay.** Add an "HTTP API" column: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~fred-release-calendar-alerts/run-sync-get-dataset-items?token=`, Body `{"releases":["{{search}}"]}`, mapping the row's search into the `releases` array. **MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "economic release calendar alerts" — the agent will find and run this actor. # Actor input Schema ## `releases` (type: `array`): One per line: a short alias for the headline release (CPI, jobs, GDP, PPI, PCE, retail sales), a numeric FRED release ID (10 is Consumer Price Index, 50 is Employment Situation, 53 is Gross Domestic Product) or any part of a release name ("Gross Domestic Product by State"). Leave empty to get every release in the window. Accepted formats: CPI, jobs, GDP, 53, "Producer Price Index". You're only charged for the ones we actually find — a miss costs nothing. ## `fredApiKey` (type: `string`): Optional. Get a free key in about a minute by creating a free FRED account (instant, nothing to wait for) at fred.stlouisfed.org/docs/api/api_key.html and paste your own key here. This actor never ships or shares a key; the key and its request limit are yours. Without a key every search comes back as one NEEDS_KEY row and nothing is charged. ## `testRun` (type: `boolean`): Turn this on to test your input on a small sample before running the full list. Turn it off to process everything. ## `onlyFound` (type: `boolean`): Only keep rows where something was actually found. Misses are always free, whether or not you show them here. ## `includeKeywords` (type: `array`): Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything. ## `excludeKeywords` (type: `array`): Optional. Drop any result that mentions one of these words. Leave empty to skip nothing. ## `maxResults` (type: `integer`): Up to 500. Caps how many release dates you get (and pay for) in one run. ## `daysBack` (type: `integer`): How many days before today to include. Release dates already past come back as PUBLISHED. 0 returns upcoming dates only. Up to 120. ## `daysAhead` (type: `integer`): How many days after today to include. FRED lists scheduled dates for roughly the next few months. Up to 120. ## `onlyNewSinceLastRun` (type: `boolean`): On: only release dates you have not been given before are returned and charged for. A release counts as new when it first appears as UPCOMING and again the first run after its date passes (PUBLISHED). Run it on a daily schedule as a release alert. Off: every matching release date is returned every time. ## `deltaName` (type: `string`): Optional. Name this search's monitoring memory so you can tell two schedules apart, or keep one memory across an input change. Leave empty to auto-derive one from your release list. ## `columns` (type: `array`): Choose which pieces of information to include in each result row. All are included by default. ## `expandRows` (type: `boolean`): When on, each release date found gets its own row instead of being grouped under its search. You're still only charged once per search, no matter how many rows it produces. ## `maxConcurrency` (type: `integer`): Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady. ## Actor input object example ```json { "releases": [ "CPI", "jobs", "GDP" ], "testRun": false, "onlyFound": false, "includeKeywords": [], "excludeKeywords": [], "maxResults": 100, "daysBack": 7, "daysAhead": 14, "onlyNewSinceLastRun": false, "deltaName": "", "columns": [ "searchSummary", "releaseCount", "truncated", "monitorStatus", "releaseDates", "source", "releaseId", "releaseName", "releaseDate", "releaseStatus", "daysUntil", "lastUpdated", "releaseUrl", "isNew", "firstSeenAt" ], "expandRows": true, "maxConcurrency": 1 } ``` # Actor output Schema ## `results` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "releases": [ "CPI", "jobs", "GDP" ], "includeKeywords": [], "excludeKeywords": [] }; // Run the Actor and wait for it to finish const run = await client.actor("accountable_eel/fred-release-calendar-alerts").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "releases": [ "CPI", "jobs", "GDP", ], "includeKeywords": [], "excludeKeywords": [], } # Run the Actor and wait for it to finish run = client.actor("accountable_eel/fred-release-calendar-alerts").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "releases": [ "CPI", "jobs", "GDP" ], "includeKeywords": [], "excludeKeywords": [] }' | apify call accountable_eel/fred-release-calendar-alerts --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/fred-release-calendar-alerts" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/GlaJXGyJmLaBPxlDD/builds/KJbCFfbT4OT8apmkL/openapi.json