Update Webhook

seatable.update_webhook
ActionDatabases & warehousesconnection required

Calls the SeaTable API with the connection's credentials.

Repoint an existing webhook at another URL, or rotate its signing secret; SeaTable wants the URL on either change.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
SeaTable
Secret shape
the base API token, or {"api_token": "…", "account_token": "…"} where the account token is only needed by the webhook operations
Config it needs
server_url, base_uuid, workspace_id, base_name
Resolved by
config.connection_id, else node.connection_id

Configuration

3 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
webhook_id
Numeric id of the webhook, as returned by seatable.list_webhooks.
numberYes—≥ 11
url
HTTPS endpoint SeaTable posts every base change to; SeaTable requires it on an update too, so repeat the current endpoint when only the secret changes.
stringYes—url format—
signing_secret
Shared secret SeaTable signs each delivery with, sent as the X-SeaTable-Signature header. Leave blank for unsigned deliveries.
stringNo—credential materialcredential

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "webhook_id": 1
}

Output

One shape.

result

FieldTypeExample
id
Numeric webhook id.
number—
url
The endpoint SeaTable posts to.
string—
dtable_uuid
UUID of the base the webhook watches.
string—
creator
Account that registered the webhook.
string—
created_at
ISO-8601 creation timestamp.
string—
{
  "created_at": "",
  "creator": "",
  "dtable_uuid": "",
  "id": 0,
  "url": ""
}

See Update Webhook run in a workflow.

In a technical demo we add the SeaTable connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.