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. Specifically, the Create operation for the Database Row resource allows users to add new rows of data into an AppFlowy database.

Common scenarios where this node is beneficial include:

  • Automating data entry into AppFlowy databases from other systems or workflows.
  • Creating new records based on form submissions, API calls, or scheduled tasks.
  • Populating databases with structured data either by mapping fields manually or by sending JSON-formatted data.

For example, you could use this node to create a new project task in an AppFlowy database whenever a new issue is created in a bug tracking system, mapping relevant fields like title, description, due date, and status.

Properties

Name Meaning
Workspace Name or ID The workspace where the target database resides. Choose from a list or specify dynamically via expression.
Database Name or ID The specific database within the workspace where the row will be created. Choose from a list or specify dynamically via expression.
Data to Send Method of providing data for the new row:
- Map Manually: Define each field's value individually.
- JSON: Provide the entire row data as a JSON object.
Properties to Send (Shown if "Map Manually" selected) A collection of fields and their values to set in the new row. Each property includes:
- Property Name or ID (field identifier)
- Type (field type)
- Value(s) depending on type (text, number, select options, date/time, URL, checkbox).
JSON Data (Shown if "JSON" selected) The full JSON representation of the row's cells to send. Must follow the expected structure with field keys and their corresponding content.
Include Document Data Whether to include additional document data (Markdown format) associated with the row.
Document Data (Shown if "Include Document Data" is true) Markdown content representing the document data of the database row.

Details on Field Types Supported in Manual Mapping

  • RichText: Text string.
  • Number: Numeric value.
  • SingleSelect: Single option name or ID.
  • MultiSelect: Multiple option names or IDs.
  • DateTime: Date/time value, optionally as a range with start and end dates, including timezone support.
  • URL: URL string.
  • Checkbox: Boolean indicating checked state.

Output

The node outputs an array of JSON objects representing the created database rows. Each output item contains:

  • json: The response data from the AppFlowy API for the created row, which includes details such as the row ID and the stored cell values.

If document data was included, it will be part of the sent data but the output reflects the API response confirming creation.

No binary data output is produced by this node.

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, fields, and rows.
  • Timezone handling uses external libraries (moment-timezone and luxon) internally for date conversions.
  • Proper configuration of workspace and database IDs is necessary, which can be loaded dynamically via provided methods.

Troubleshooting

  • Missing Field Values Error: If "Map Manually" is selected but no properties are provided, the node throws an error indicating no field values were given. Ensure at least one field is mapped.
  • Missing Date Values: For DateTime fields, if a date or date range is expected but not provided, an error will occur. Make sure to supply valid ISO 8601 date strings.
  • Invalid JSON Data: When using the JSON input method, malformed JSON will cause parsing errors. Validate JSON syntax before execution.
  • API Authentication Errors: If the API key credential is missing or invalid, requests will fail. Verify credentials in n8n settings.
  • Field or Database Not Found: Selecting a workspace or database that does not exist or is inaccessible will result in API errors. Confirm correct IDs are used.
  • Timezone Issues: Incorrect timezone values may lead to unexpected date/time conversions. Use the provided timezone options or leave default.

Links and References

Discussion