Webhook triggers from record buttons

Feature Requests
1

Problem

Currently, AnyDB’s Make integration only supports passive automation (create/update events). There’s no way to trigger external automations explicitly from a record via a user action.

I understand that this feature can be emulated with a checkbox field that triggers a passive event when checked, but I think a button is a more elegant solution here.

Requested feature

Add button-type fields that can fire outgoing webhooks, with:

  • Configurable webhook UI

  • Record ID + selected fields sent in payload via HTTP Headers

  • Status feedback (loading/success/error)

Use cases

  • Order processing: “Send to fulfillment” → triggers Make scenario

  • Approvals: “Approve” → notifies external systems

  • Data enrichment: “Fetch data” → calls API and writes back results

Why it matters

This would enable AnyDB to function as a true operational backend, not just a database. It’s a key feature for replacing traditional SaaS tools with AnyDB-powered workflows.

2

Good request, and you’re right. A checkbox is a workaround, not a real solution.

We do plan to support button-type cells, but they will trigger workflows, not fire raw webhooks directly.

The model will be:

Button → Workflow → Actions

This lets us support:

  • Explicit user-initiated actions
  • Clean integration with Make and other webhooks
  • Record context in the payload (record ID, fields)
  • Proper status feedback (running, success, error)
  • Reusable logic across buttons and other triggers

Your use cases like Send to fulfillment, Approve, and Fetch data are exactly what this is designed for.

Button cells and workflows are being designed together and are on the near-term roadmap.

1 Like