AppFlowy Trigger icon

AppFlowy Trigger

Starts the workflow when AppFlowy events occur

Overview

This node triggers workflows in n8n based on events occurring in AppFlowy, a workspace and database management platform. It listens for two types of events: when a row is added to a database or when a row is updated in a database within a specified workspace.

Common scenarios where this node is useful include:

  • Automating notifications or actions when new data entries are added to an AppFlowy database.
  • Syncing updated data from AppFlowy databases to other systems or services.
  • Monitoring changes in project management or data tracking tools built on AppFlowy.

For example, you could use this node to trigger a workflow that sends an email alert whenever a new task is added to a project database or updates a CRM system when customer information changes.

Properties

Name Meaning
Event The type of event to listen for. Options: "Row Added to Database" or "Row Updated in Database".
Be aware that it may take up to one minute for a changed row to be reflected in the API response A notice shown only when "Row Updated in Database" event is selected, informing users about potential delay in update reflection.
Workspace Name or ID The workspace to monitor. Can be selected from a list or specified via expression.
Database Name or ID The database within the workspace to monitor. Depends on the selected workspace. Can be selected from a list or specified via expression.
Include Document Data Whether to include the full document data of each row in the output. Boolean value.
Simplify Whether to return a simplified version of the response instead of the raw data. Boolean value.

Output

The node outputs JSON data representing rows from the specified AppFlowy database that triggered the event:

  • For "Row Added to Database", it outputs details of newly added rows.
  • For "Row Updated in Database", it outputs details of rows updated since the last check.

If the "Include Document Data" property is enabled, the output includes the full document content of each row; otherwise, it contains metadata only.

If "Simplify" is enabled, the output is a streamlined version focusing on essential fields rather than the complete raw API response.

The output is an array of JSON objects, each representing a row with its associated data.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the AppFlowy API.
  • Uses AppFlowy REST API endpoints to fetch workspaces, databases, and row data.
  • Relies on the moment-timezone library for handling date/time calculations related to polling intervals.
  • Requires proper configuration of workspace and database selections to function correctly.

Troubleshooting

  • Delay in detecting updated rows: The node notes that updates may take up to one minute to appear via the API. This is inherent to the AppFlowy API's update propagation and not a node error.
  • No data returned on manual trigger for "Row Added to Database": The node does not support manual triggering for this event type and will return no data if manually executed.
  • Invalid workspace or database IDs: Selecting or specifying incorrect workspace or database identifiers will cause API requests to fail. Ensure these are valid and accessible.
  • API authentication errors: If the API key credential is missing or invalid, the node will fail to connect to AppFlowy. Verify credentials are set up properly.
  • Polling state issues: The node stores state between polls to detect changes. Clearing workflow static data or resetting the node may cause missed events or duplicate triggers.

Links and References

Discussion