AppFlowy icon

AppFlowy

Consume AppFlowy API
Join our community

Actions6

Overview

This node integrates with the AppFlowy API to manage database rows within a specified workspace and database. The "Get Many" operation for the "Database Row" resource retrieves multiple rows from a selected database, optionally filtering by update time, limiting the number of results, and including detailed document data.

Common scenarios where this node is beneficial include:

  • Extracting bulk data from an AppFlowy database for reporting or further processing.
  • Synchronizing database rows with other systems by fetching updated records since a certain date.
  • Automating workflows that require batch retrieval of database entries.

For example, you could use this node to fetch all rows updated after a specific date to trigger notifications or data syncs only for changed records.

Properties

Name Meaning
Workspace Name or ID The name or ID of the workspace containing the target database. You can select from a list or specify dynamically using expressions.
Database Name or ID The name or ID of the database from which to retrieve rows. Depends on the selected workspace.
Include Document Data Whether to include the full document data (e.g., Markdown content) of each database row in the output.
Return All Whether to return all matching rows or limit the number of results.
Limit Maximum number of rows to return if not returning all. Must be at least 1.
Simplify Whether to return a simplified version of the response instead of the raw API data. Simplified data is easier to work with in most cases.
Filter Type of filter to apply when retrieving rows. Options:
- None: no filter applied.
- Updated After: only rows updated after a specified date/time are returned.
Updated Time An ISO 8601 date/time string used when the "Updated After" filter is selected. Only rows updated after this timestamp will be retrieved.

Output

The node outputs an array of JSON objects representing database rows. Each object corresponds to one row and contains its data fields.

  • If Include Document Data is enabled, the output includes the full document content associated with each row.
  • If Simplify is enabled, the output is a cleaned-up, user-friendly version of the data rather than the raw API response.
  • The output does not include binary data.

Example output structure (simplified):

[
  {
    "id": "row_id_123",
    "cells": {
      "Field1": "Value1",
      "Field2": "Value2"
    },
    "document": "Optional markdown content if included"
  },
  ...
]

Dependencies

  • Requires an active connection to the AppFlowy API via an API key credential configured in n8n.
  • The node depends on the AppFlowy API endpoints for workspaces, databases, and database rows.
  • Uses internal helper functions to handle API requests and data formatting.
  • No additional external services beyond AppFlowy are required.

Troubleshooting

  • No rows returned: Check that the workspace and database IDs are correct and that there are rows available. If using the "Updated After" filter, ensure the date is correctly formatted and that rows have been updated after that date.
  • API authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Limit ignored or too many results: Ensure "Return All" is set appropriately; if false, the "Limit" property controls the maximum number of rows returned.
  • Missing document data: Confirm that "Include Document Data" is enabled to receive full document content.
  • Invalid date/time format: When using the "Updated After" filter, provide a valid ISO 8601 date/time string.

If errors occur during execution, the node either stops or continues based on the "Continue On Fail" setting, providing error messages per item.

Links and References

Discussion