What's new in Hookie
Changes that have reached production, newest first, by the day they shipped.
See tenant usage in the admin list
The Admin tenant list now shows each workspace’s events, deliveries and agent runs for the current month, alongside its last retained event. Operators can spot metered activity without opening every tenant. Unavailable usage readings are shown separately from zero usage.
Build Workspace Brain pipelines visually
Workspace Brain’s Pipelines tab now has an interactive workflow builder. Select sources, processing steps and destinations on the canvas to edit their settings, add filters and field mappings, and reorder processing steps. Project datasets, uploads and S3 sources use guided forms, with validation before you save.
Connect an agent dialog fits smaller screens
The Connect an agent dialog now keeps its instructions and copy buttons inside the window. Long Claude Code commands scroll within their code field on smaller screens, in both light and dark themes.
Multi-step Brain queries on large workspaces
Following relationships two or more steps out from a record, in the Brain and for connected agents (
query_graph_context), now works on large workspaces. On a 50,000-record workspace these queries had started failing as “temporarily unavailable”; the same walk now answers in milliseconds.A wider Workspace Brain sidebar, a taller grid, round canvas nodes and clearer deletes
Drag the data workspace’s sidebar wider, up to a quarter of the window, so long table names fit on one line; it remembers your width, works from the keyboard, and a double-click puts it back. The Workspace Brain’s Grid now fills the page. Each Project Inputs connection has a Delete button that stops the sync and keeps every row and record. In Edit record, Delete is now a red button opposite Save record that asks before it deletes. The tabs read AI Memory and Project Inputs. On the Brain canvas, tables and records are now circles, sized by how many records they hold, with the full name on hover.
Plan arrangements made by Hookie stay in place
When Hookie’s team sets your workspace’s plan by hand, for example a comp or a support arrangement, it now stays in place until it is cleared or reaches the end date agreed with you, even if your subscription changes in the meantime. Your billing details show the arrangement while it lasts, and your audit log records every plan or add-on change Hookie makes, with the reason.
Workspace tables keep up with busy webhooks
When a burst of events briefly overloads a workspace database, Hookie now retries the write within seconds instead of leaving it for the next scheduled retry, which could hold a table up to 25 minutes behind its dataset. A capture that still has to wait says so where you can see it, and is never written twice. Import existing records now tells the records it imported apart from those already in the table.
Delete anything you created, and deletion that reaches every copy
Deleting a project now permanently deletes everything in it: its records, raw submissions, deliveries and their attempts, workflow runs and AI output, instead of keeping them unattributed. Deleting a record (or purging a dataset) also removes the rows a data workspace table or a Brain pipeline copied from it and what the Workspace Brain derived from them. You can now delete a single delivery, a single workflow run, a workspace table (type its name to confirm), a table’s data connection, a saved view, a dashboard and an S3 source’s keys from the console, and connected agents have matching tools, including
delete_projectandpurge_dataset. The audit log records each deletion and who made it, never what was deleted.Record history: who changed a record, through what, and when
Every record now has a History panel. On a workspace table record it lists each change: who made it, through what (a console session, a connected agent, an API key by name, a table input, a workflow run, a Brain pipeline or a knowledge graph change), when, and which fields changed from what to what. On a project record it shows how the record arrived (the ingest key or endpoint, and the submission) and who deleted it and why (on its own, a dataset purge or a project delete). Deleting a record keeps who created, changed and deleted it, and removes its values from the history. Connected agents can ask the same question with the
get_record_historytool, and the audit log now names the credential that acted, so an API key’s actions are no longer credited only to whoever created the key.Press Enter to save a dialog
In a dialog’s text field, Enter now does what the primary button does: create, save, add. Delete and other confirmation dialogs still need a deliberate click, and Enter in a multi-line field still starts a new line.
A new look for the console and the site
The console and hookie.ai have Hookie’s own design now, in the spirit of Apple’s Liquid Glass: the system font, rounded buttons and fields, a frosted-glass header, sidebar, dialogs and menus, segmented tabs, native date pickers, cleaner outline icons and smoother motion, in both dark and light themes. Pages load faster too: the console’s stylesheet is a fraction of its old size and neither site downloads a web font any more. Everything works as before. The sidebar still collapses to icons, and on a phone it slides in from the menu button.
Personal AI memory from Claude, ChatGPT and their coding agents
Connect Claude, Claude Code, ChatGPT or Codex to Hookie and your agent can keep what it learns about you as memory artifacts in your workspace, filed under the chat they came from, and recall them in your next conversation. Find them under Workspace Brain → AI Memory. They are private to you: link one to a project and share it, and your team and their agents can read it too.
Workspace Brain ingestion pipelines
The Workspace Brain has its own ingestion pipelines, separate from your projects’ workflows, so the Brain screen only shows what feeds the Brain. A pipeline curates a project dataset into a workspace table: filter the records, map their fields, run a backfill, and new records keep flowing in while it is enabled. Connected agents can build and run pipelines over MCP.
Documents, S3 sync and search in the Workspace Brain
Drop plain-text files into the Brain, or sync them from an S3 bucket, and they are stored, split into passages and indexed for agents to search. Changed files replace their old version, and deleted files leave the Brain. Search returns the best-matching passages from documents you have included, and the same search is an MCP tool. Storage, embedding, search and sync allowances are hard limits, shown on the Documents tab.
Ultimate plan and the Brain add-on
Ultimate is $100 a month, flat. It has everything in Team plus the document Brain: 10 GB of storage, 20 million embedding tokens and 100,000 searches a month, and up to 10 S3 sources. The document Brain is also a $10-a-month add-on to Pro and Team. Tables, the knowledge graph and project pipelines stay included with Pro and Team, as before.
Safer platform security review
Operators can investigate workspace activity from a new Security tab, record review decisions, place independent security holds and revoke workspace keys and agent grants. Actions require a reason and exact workspace confirmation, protect against stale edits and retain an audit trail. Tenant browsing now reaches beyond the former 200-workspace limit.
More room for marketing introductions
The CLI and other marketing pages give introductory text more of the desktop page, with full-width copy on smaller screens and consistent spacing in both themes.
Build context for your business AI agents
Explore the new knowledge graph overview and client-context pipeline guide. See how webhooks, WebSocket listeners, PostgreSQL sources and workflows prepare curated knowledge for agents, with examples for business teams, small businesses and freelancers. The guides explain how focused retrieval can reduce prompt size and processing time, and how to review the facts and relationships your agents use.
More room for your data
Data workspace now uses more of your screen, with rounded panels, a compact header and refreshed table and dashboard styling in both themes. Open Browse data to switch tables, dashboards or the Workspace Brain, then Hide sidebar to give your work the full width. Filters and editors stack comfortably on smaller screens.
Explore and curate your Workspace Brain
Workspace Brain now opens with a map of your included tables and their saved relationships. Select a record to explore connections across tables, filter relationship types, and expand the canvas. Choose which tables and individual records belong in the Brain; excluded data stays in its source table and is omitted from graph discovery and agent context. Table choices cover future imports, and individual exclusions are remembered when you include a table again.
Consistent reads through regional database replicas
Webhook processing, API requests and queued work can now use regional D1 read replicas after an initial read of the latest primary state. Reads within an operation see its committed writes, and each new request or queue message starts fresh so prior credential revocations and workspace changes are visible. Writes remain on the primary database.
More room to build workflows and explore knowledge
Workflow and knowledge canvases now use the site’s rounded surfaces, softer borders and clearer selection states. The workflow builder fills the available width, with a searchable step library and collapsible properties. Expand either canvas to use the screen while keeping your workflow edits and undo history. The knowledge graph also opens with its table browser tucked away, and supports inspecting nodes in the expanded view.
Connected knowledge for people, workflows and AI agents
Pro and Team data workspaces now include a knowledge graph. Edit table records in a spreadsheet, connect knowledge nodes visually, preview focused agent context, and inspect workflow execution paths. Agent and workflow changes are consolidated asynchronously; conflicting edits keep their proposals for review. Workflows can fetch graph context before AI calls or queue updates, with explicit project permissions and export of pending changes.
A dedicated data workspace for tables, dashboards, workflows and AI
Pro and Team workspaces can keep structured data in their own database. Create typed tables, edit records, save filtered and sorted views, and build dashboards with counts, totals, averages and grouped charts. Connect datasets from webhooks or data sources with visual field mappings, then use table records in workflows and connected AI agents. Imports preserve your edits, and your tables are included in workspace export and deletion.
Safer event recovery, browser privacy and form submissions
Large webhook uploads are rejected while streaming, and replayed events retain their original timestamps so trigger rules behave consistently during recovery. Fan-out across many datasets no longer exceeds the database parameter limit. Agent tokens must include an expiry, and invalid IP allowlists are rejected before replacing a working restriction.
Recently opened pages are now private to each account and workspace in the browser. Theme switching works when browser storage is blocked, and Markdown responses preserve cache variation headers. Forms client 0.2.1 keeps timeouts and cancellation active until the response body finishes and reports interrupted responses as transport failures, with safe idempotent retries.
Starter is $4 a month and bigger, Pro is $10 a month, Team stays $30 flat
Starter is now $4 a month flat and includes more: 35,000 events a month (was 25,000), 50,000 deliveries (was 40,000), 4 outbound destinations (was 3) and 150,000 AI tokens (was 100,000). Pro is now $10 a month flat, with the same allowances as before. Team is $30 a month flat for up to 10 members, billed as a single price; adding or removing a member never changes it.
Endpoints whose slug ended in -v and a number were unreachable by key
On the key-authenticated route,
/v1/webhooks/{key}/{slug}, a slug ending in-vand a number (for exampleorders-v2) names a version of another endpoint, so an endpoint created with such a base slug answered 404 there for good. About one console-created endpoint in 1,870 got one, because the generated slug ends in four random characters. New endpoints can no longer be given such a slug, generated slugs avoid the pattern, and endpoints already stored that way now answer on the key route. The endpoint’s own URL was never affected.Retry policy, circuit breaker and failure alerts for each destination
A destination can now have its own retry policy: on Pro and Team, a linear or exponential schedule of up to 50 attempts over 7 days (Free keeps today’s 8 attempts over about a day; attempts past the eighth count against the monthly delivery allowance). An optional circuit breaker pauses a destination after a set number of failed attempts in a row, holds its events instead of dropping them, tests it again on its own and resumes it when a delivery succeeds. Email and Slack alerts tell the workspace when a destination is paused or a delivery dead-letters, at most once an hour per destination. Set them in the destination’s Retries, circuit breaker and alerts dialog, the API or the
update_destinationMCP tool.Team is $30 a month flat for up to 10 members; Free grows to 10,000 events; paid plans keep data 90 days
Team is now one flat price of $30 a month for a workspace of up to 10 members, instead of $39.99 per member. Adding or removing a member no longer changes the bill, and an eleventh member cannot be added. Free now includes 10,000 events and 10,000 deliveries a month and keeps data for 30 days, and every paid plan (Starter, Pro and Team) now keeps data for 90 days. Longer retention only keeps more: nothing existing is deleted, and a paid workspace that moves to Free keeps its 90 days for 7 more days first.
Scripted transforms: reshape a payload with an expression
Attach a transform to an endpoint to reshape the payload before it is routed and stored, or to a destination to reshape just what that destination receives, add headers, or drop the delivery. Transforms are JSONata expressions that run in a sandbox with step, size and depth limits, with no network, secrets or other data in reach. Test one against a sample first: the test endpoint returns the output, log lines, steps used and timing without storing anything. If a transform fails, the original submission is kept, marked failed and listed on the Errors tab, and Hookie routes it again once you fix the script; a failing destination transform fails that delivery visibly and retries it. Every edit is a new version you can restore. Free includes one transform; Starter 3, Pro 20, Team 100. Transforms are managed through the admin API for now; the console editor and MCP tools are next.
Forms client 0.2.0: timeouts, Turnstile tokens and clearer errors
@hookieai/forms0.2.0 adds atimeoutMsoption (30 seconds by default), aturnstileTokenoption for forms submitted from a component rather than a plain<form>, anonRetrycallback, and areasonon every failure (network,timeoutorabortedas well as Hookie’s own). It is fully backward compatible, ships typed results, and its README now has Astro, Svelte and Vue examples and explains how file fields are stored.Forward live events to localhost with `hookie listen`
hookie listen --forward http://localhost:3000/hookssends your project’s live events to a server on your machine and prints each one’s local status and latency, so you can build a webhook handler without exposing it. Narrow it with--webhookor--dataset, use--jsonfor one object per line, and it reconnects and resumes without forwarding an event twice. It works with your login or an ingest key, never sends an endpoint’s URL or a credential to your server, and a failure on your side does not affect the real delivery. The live stream is best-effort, so a long disconnect is reported as a gap.Data API keys are revoked when their creator leaves
When a workspace member is removed or leaves, their active Data API keys for that workspace are revoked. Keys from other members and other workspaces continue working.
Outbound credentials stay with their configured destination
Changing a webhook destination’s host now requires re-entering or clearing its stored authentication and secret headers. URL-embedded credentials are refused, and credentials echoed by receivers are redacted from delivery and telemetry errors.
Large data pages and exports are more efficient
The Data API supports cursor paging for large datasets while keeping existing offset clients working. Large totals are explicitly marked when capped, and workspace exports page delivery attempts efficiently.
API requests are bounded against oversized batches
Hosted MCP calls now limit legacy batch size, and MCP/admin JSON request bodies have a byte ceiling. Authentication and authorization failures no longer consume idempotency capacity.
Session refresh and endpoint network restrictions are preserved
Refreshed sign-in sessions now continue across API requests, restricted endpoint versions retain their IP allowlists, and an allowlisted request without a client IP is refused.
Workflow HTTP headers are protected
Workflow HTTP-step header values are encrypted when saved and masked on reads. They are not included in project configuration exports; workspace exports redact them. Existing definitions continue to run and are encrypted when next edited.
Read-only members no longer receive endpoint credentials
Endpoint URLs are available only to members with write access, and sending a test event requires write scope because it creates and delivers a real event. Ingest keys continue to stream only their own project’s live events.
Project-scoped API keys cannot create sibling projects
A project-scoped API key can no longer use that project’s configuration-clone action to create a new workspace project. People and unscoped keys keep their existing clone access.
Workflow runs from the retired engine cannot be retried
Workflow runs that started before the move to the current workflow engine finished on the old engine, and that engine is now gone. Such a run can no longer be retried; the console and the API say so, and starting the workflow again runs it on the current engine. Nothing else about how workflows run has changed.
Agents cannot mint Data API keys or change what the Data API publishes
An AI agent connected to a workspace can no longer create a Data API key or change which data the Data API publishes. It gets the same refusal an agent already gets for creating API keys, and a person can make either change in the Hookie console. An agent can still list the Data API and revoke a key.
Deliveries stop at once when the host cannot be reached
A
508from your URL means the event has already passed through Hookie eight times, so the delivery is marked dead on its first attempt. A530that Cloudflare reports as an origin DNS error means the host name does not resolve, and that is dead at once too. Retrying either would not change the answer.Disabling or deleting a destination keeps its queued deliveries
Disabling a destination pauses its queued deliveries, and they go out when you enable it again. Deleting it cancels them, so they are not sent and are not marked dead.
An empty dataset filter is refused
The API refuses a dataset filter that is an empty list, since it would mean nothing rather than everything. A destination already saved that way receives nothing until you change its filter. Leave the filter unset to receive every dataset.
Empty JSON bodies are refused
A request with an empty JSON body is refused with
422after its signature is checked, instead of returning201with no record stored.Endpoints can dedupe on a body field
An endpoint can now dedupe on a field in the request body, set with
dedupe_path. Idempotency-Key headers and provider delivery ids were already used for this, and nothing changes for an endpoint that does not set it.Record sources no longer carry the endpoint slug
New records and submissions store
sourceaswebhook:and the endpoint’s id, not its public slug, so the slug no longer appears in search, exports or the_sourcecolumn. Records stored before this release keep the value they were given.Configuration exports leave out endpoint URLs
A configuration export writes a destination that points at one of your endpoints as an endpoint reference rather than its URL, so the export holds no live endpoint slug.
hookie applyresolves the reference in the project it applies to.Workflow conditions can group with any and all
A workflow condition can now be a group,
anyorall, nested two levels deep. Simple conditions work as before.Connected agents see every tool, and scope is checked on each call
A connected agent is shown the full tool list. A call above the scope it was granted is refused, and the error names the scope it needs. A wider grant applies from the agent’s next call.
Search times match exactly
sinceanduntilin search are read as exact moments, and both include the moment they name.A delivery lookup returns its record
Looking up a delivery returns the id of the record it sent, so you can go from a delivery to its record without searching.
hookie.ai publishes discovery cards for AI agents
hookie.ai now carries the cards AI agents look for: an A2A agent card, an MCP server card and a skills index. Webhook deliveries from Hookie are signed with Web Bot Auth (RFC 9421, Ed25519), so a receiver can check that a request really came from Hookie.
hookie.ai reads well to AI agents
An AI agent that asks for Markdown gets the page as Markdown, and the homepage points agents at the API catalog and the other machine-readable documents. The API catalog lives at
/.well-known/api-catalog, and/auth.mdnames every route to a Hookie credential in one file: self-registration, a connected agent over OAuth, and WorkOS Agent Auth.Analytics across every project
A new Analytics page under Get started puts the whole workspace on one page. Pick a project or all of them and a time range of 24 hours, 7 days or 30 days: the charts and cards follow, and four tabs break the same numbers down by project, endpoint, workflow and dataset. Datasets show how much data they hold and their share of everything stored. Deliveries are counted per project, because a delivery is not tied to the endpoint that received the event.
Install the CLI and the forms package from npm
@hookieai/cliand@hookieai/formsare published on npm, and the console and docs show the install lines for them.A new console layout and a Home with analytics
The side navigation groups an open project’s pages under Build, Deliver and Observe, and filters as you type: press
/or ⌘K. Home now charts events received, deliveries sent and AI runs over the last 24 hours, 7 days or 30 days, each with its change on the period before, and lists what needs you, such as a failing destination or a limit you are close to. Its search box reaches any project, page or setting, and the pages you opened last are one click away. Buttons, tiles and dialogs are slightly rounder.Protect a public HTML form with an endpoint
An endpoint can now take a plain HTML form directly. A hidden honeypot field drops bots without costing an event, a Cloudflare Turnstile secret makes every submission pass verification, and declared form fields refuse a submission that is missing one with a 422 naming each field. A form posted with no redirect URL lands on a thank-you page.
Create and test a form from the CLI
hookie forms initsets up a contact, newsletter, waitlist, feedback or survey endpoint with its fields, a honeypot, allowed origins and a redirect, and writes a ready HTML, React or Astro form into your project.hookie forms testposts a sample built from the endpoint’s fields.The website shows the new console
Every console picture on hookie.ai is the current console, in your theme, and the features page describes Home and the project Errors tab.
Invite your team: links, roles and ownership transfer
Owners and admins invite teammates with a shareable link made for one role — admin, developer or viewer. A link works once and expires after 7 days. Roles can be changed, members removed, ownership transferred, and anyone who belongs to more than one workspace switches between them from the header. The Team plan is on sale.
Filtered events are kept, and a project Errors tab lists them
A payload that an endpoint’s own criteria reject, or that could not be routed, is no longer silently dropped: it is kept, flagged, and listed in the project’s new Errors tab.
Fixes to the legacy key-and-slug ingest route
An event sent through the older
/v1/webhooks/{key}/{slug}route is filed under the endpoint it was sent to, and an endpoint with a malformed rule answers as a routing failure rather than a server error.The marketing site lines up on phones
The navigation, hero text and buttons sit on the same margins at every phone width.
Verify the provider's signature on an endpoint
An endpoint can check the signature of the provider sending to it — Stripe, GitHub, Shopify, Slack, Standard Webhooks or your own HMAC — before anything is stored, and refuse what fails. The setting travels with project export, import, clone and
hookie apply.Admin API keys, rate limits, idempotency and versioning
Automate the admin API with workspace API keys that carry their own role. The admin API and the MCP server are rate-limited, accept idempotency keys for safe retries, and are versioned.
See every delivery attempt and the whole trace
A live view in the console, the full trace of an event through rules, workflows and deliveries with its payloads and errors, every failed delivery attempt kept with its response, and per-destination delivery metrics.
Customer portal: endpoint management, replay and branding
Your customers manage their own endpoints from the portal, see why a delivery failed and replay it, and get examples and a verification guide covering both Hookie-Signature and Standard Webhooks. The portal can carry your branding and be embedded in your own app.
Rule editor, project export and import, and `hookie apply` fixes
Rules are edited in a form with more operators. A whole project can be exported, imported and cloned.
hookie applyandhookie diffchange a destination’s URL and name in place and read nested YAML correctly.Over-limit resources pause on downgrade and resume on upgrade
Moving to a smaller plan pauses what no longer fits instead of deleting it, and upgrading resumes it. Your previous plan’s retention window is kept for 7 more days after a downgrade, so you have time to export or upgrade.
Console polish and first-run guidance
Export a whole dataset, see errors inside the dialog that caused them, edit and really delete things, and get guidance on a new workspace’s first steps. You can add a payment method during a trial.
An ingest key's default dataset catches what no rule matches
Events that match no rule land in the ingest key’s default dataset instead of being dropped. Cron and WebSocket triggers with no dataset store their unmatched events in
default.Workflows and triggers are more reliable
Workflows can be deleted for good. A database source never loses a polled row or charges for it twice. The background sweep routes an event whose record was never written, AI-trigger and workflow output is stored atomically, and a failed WebSocket trigger shows its last error.
Clearer limits and warnings
Home warns at 80% and 100% of the monthly AI trigger runs, the rate limits are stated as they are enforced, and the console stops offering features that are not available yet.
Security and correctness fixes
A workflow run’s context is redacted wherever the API returns it. Single sign-on says it is not available instead of showing a form that cannot work. Number comparisons in conditions accept numbers sent as text. The console always loads its newest version, and the admin API answers 405 for a method a route does not serve.
Team is $39.00 a seat
The Team plan is $39.00 a seat each month, with 300,000 events a month.
Trial checkout keeps your remaining trial days
Subscribing during a free trial keeps the days you have left before the first charge.
Security, changelog and real screenshots on hookie.ai
This site gained a security page, this changelog and real console screenshots. A customer portal can now be removed for good, revoking its links and cancelling its destinations.
Erase and export your data, or close your workspace
Delete a single record with every copy Hookie keeps of it, purge a whole dataset, export everything in a workspace as one file, or close the workspace: it is suspended at once and deleted 14 days later.
Destination headers, auth and payload shaping; failing destinations flagged
Add custom headers and authentication to a destination and reshape the payload it sends — enough to post straight to Slack. A destination whose deliveries keep dying is flagged in the console and, after a sustained run of failures, switched off with an optional alert, holding new deliveries until you re-enable it.
Standard Webhooks signatures
Every delivery is signed with both Hookie-Signature and the Standard Webhooks headers, and the docs carry verification snippets beyond Node.
Ingest: request metadata, HTML forms, provider dedup and handshakes
Each event keeps its request metadata. A plain HTML form can redirect to your thank-you page and a browser
fetch()is answered with CORS. Provider retries are de-duplicated, URL-verification handshakes are answered, and rejected requests are logged.Database sources, AI triggers in the console, and workflow debugging
Database sources work, AI triggers are managed in the console, and a workflow instance can be inspected step by step.
Connected agents can do more, and say what they need
An agent refused for lack of a scope is told how to widen it, the scope screen shows what each scope allows, and MCP gained tools for sources, triggers, AI agents and portals.
Billing details, workspace rename and canonical links
See your billing details from Stripe in the console, and rename a workspace without breaking its old URL slug.
Clearer limits in the console and on pricing
Pricing discloses the soft caps and allowances, and the console says when you reach one.
Reliability: stuck workflows, delivery latency and large datasets
Stuck workflow runs are reaped, delivery latency is recorded, sorting a large dataset stays fast, and several smaller ingest-key, Data API and trigger fixes landed.
A more accessible console
Headings are in order inside tabs, error states have a heading, Observability’s controls are labelled, and the footer sits outside the main landmark.
Suspension stops everything
A suspended workspace stops ingest, delivery, triggers, sources, running workflows, portal writes, open streams and console changes together. Deliveries are paused rather than lost.
Workflows: a visual builder, runs on the graph, and Cloudflare Workflows
Workflows are built on a canvas: drag steps in, connect them, and fill each one in a side panel. Pick a run and every step shows whether it completed, is waiting or failed. Workflows run on Cloudflare Workflows, gained HTTP, set and transform steps, and share one condition syntax with rules; cron triggers take a time zone.
Delivery recovery: bulk replay, secret rotation overlap, per-destination limits
Replay every failed delivery in a time window at once, from the console, the CLI or an agent. Rotating a destination’s signing secret signs with both the old and the new secret for 24 hours. Each destination can set its own timeout, rate limit and concurrency cap.
Ingest keys in the console, endpoint rotation and allowlists
Ingest keys are managed from the console, with expiry. Endpoints can be edited and their URLs rotated. IP allowlists apply per key, per endpoint and per workspace, and the workspace allowlist can be read and is only changed on purpose.
Deliveries past the monthly allowance are held, not dropped
When a workspace uses its monthly delivery allowance, further deliveries are held instead of lost. Once there is room — after the 1st of the month (UTC) or an upgrade — send them from the Deliveries tab, and they go out oldest first.
Retention for runs and the audit log; audit export filters
Workflow runs, AI trigger runs and settled deliveries are pruned when they pass the plan’s retention window. The audit log is kept for at least a year, cannot be altered, and can be filtered before export.
One customer portal per project, and a safer one
Each project has one customer portal, configured in its Settings. A portal delivers only the datasets it exposes, links are exchanged for a short-lived session cookie, tokens are looked up by their full hash, and the portal API is rate-limited.
Connect your own coding agent
The console’s built-in assistant is gone. Connect an agent hands your own MCP client the hosted MCP URL and the steps to authorize it. A connected agent starts read-only, and never reaches billing or platform administration.
Hookie's own sign-in and sign-up pages
Sign in with an emailed one-time code, GitHub or Google on Hookie-branded pages. Only the social sign-ins an environment has enabled are offered.
A read-only Data API for each project
Publish chosen datasets and columns from a project, issue per-project keys, and read the records from your own code.
Broadcast Logs: send a project's logs and traces over OTLP
Connect an observability vendor — Datadog, Grafana Cloud, PostHog, Sentry, or your own OpenTelemetry Collector — and a project’s logs and traces are forwarded to it. Event payloads and AI prompts are not sent.
AI usage is metered per plan and logged
Every AI call counts against a monthly token allowance for the plan, and each call’s prompt, input and output is kept in the AI call log for the plan’s retention window.
One table everywhere, and a more accessible console
Every list in the console is the same table, with 25, 50 or 100 rows a page. Record views belong to datasets, and records page on the server. Every page has its own title and moves focus to its heading, and times show in your own time zone.
Ingest: disabled endpoints answer 503, and 429s carry Retry-After
A disabled endpoint answers 503 rather than 404, rate-limit refusals say when to retry, and plain text bodies are accepted.
Trigger limits per project
A project can have up to 10 cron triggers and 5 WebSocket triggers.
Security fixes: redirects, CSV exports, uploads
Deliveries never follow a redirect. CSV exports neutralise spreadsheet formulas and carry a UTF-8 byte-order mark. A multipart submission no longer stores uploaded file bytes.
Fonts are served by Hookie
Both sites serve IBM Plex themselves instead of loading it from Google Fonts.
Every subprocessor is listed
The Privacy Policy lists every company that processes personal data for Hookie, with what it handles and where.
Fixes from a round of QA
An endpoint’s own criteria and mappings apply on its public URL. A body with no fields is refused rather than acknowledged and dropped. A receiver that refuses a request is not asked again, and a delivery that loops back into Hookie is stopped. A disabled destination pauses its deliveries and a deleted one cancels them. Search is case-insensitive beyond ASCII. Record views can show nested fields. The CLI is installed from the console and manages your account and projects.
Deliveries retry for about a day, and failures say why
A failed delivery is retried with backoff for about a day before it is given up, and the Deliveries tab shows why each one failed and can filter to them. An acknowledged event is delivered even if the first attempt to hand it on fails. A replay of a replay works.
An endpoint URL writes only to its own dataset
A public endpoint URL can no longer be pointed at another dataset by adding a path segment. This was a breaking change for anyone relying on it.
Security fixes for streams, allowlists and signatures
A live stream opened with an ingest key sees only that key’s project. The project IP allowlist is enforced. Inbound signatures expire after five minutes, and rotating a signing secret works.
Cron and WebSocket triggers in the console
Cron and WebSocket triggers are listed, paused and deleted in the console, and their events are metered like any other ingest.
The hookie CLI
hookiemanages your account and projects from a terminal, with everything the console can do, and the site has a page for it.Console fixes
Sign-out, sign-in errors and the sign-up trial are back. A secret shown once no longer blanks the console, project tabs load when opened and can be refreshed, and Home’s quota gauge reads the same counter ingest enforces.
The new console
The previous console is retired: the console built on IBM’s Carbon Design System, in dark and light themes, is the only one, with a docked side navigation that shrinks to a rail. The marketing site moved to Carbon’s foundations and has a mobile menu.