SeaTable Trigger icon

SeaTable Trigger

Starts the workflow when SeaTable events occur

SeaTable Trigger

AI-generated

Overview

This node triggers workflows based on events occurring in SeaTable, such as new rows, updated rows, or new digital signatures. It is useful for automating processes that depend on changes in SeaTable data, like notifying users of new entries, syncing data, or processing digital signatures automatically.

Use Case Examples

  1. Trigger a workflow when a new row is added to a specific SeaTable table and view.
  2. Trigger a workflow when a row is updated in a SeaTable table, optionally filtering by view.
  3. Trigger a workflow when a new digital signature is added to a specified signature column in a SeaTable table.

Properties

Name Meaning
Poll Times Specifies the times at which the node should poll SeaTable for events, with options for various intervals and custom cron expressions.
Event The type of SeaTable event to trigger on: new row, new or updated row, or new digital signature.
Table Name The name of the SeaTable table to monitor for events.
View Name The name of the SeaTable view to monitor, applicable for new or updated row events.
Signature Column The digital signature column to track, applicable for new signature events.
Simplify Whether to return a simplified version of the response instead of raw data.
Return Column Names Whether to return column keys (false) or column names (true), applicable for new or updated row events.

Output

JSON

  • _id - Unique identifier of the row or signature event.
  • _ctime - Creation time of the row or event.
  • _mtime - Modification time of the row or event.
    - Data fields from the SeaTable row or signature column, with keys or names depending on settings.

Dependencies

  • SeaTable API with appropriate credentials

Troubleshooting

  • Ensure the SeaTable API credentials are correctly configured and have necessary permissions.
  • Verify that the specified table name, view name, and signature column exist and are accessible.
  • Check the polling interval settings to avoid missing events or excessive API calls.
  • If no events are detected, confirm that data changes occurred after the last poll time.

Links

Discussion