Overview
This node integrates with Ragic, a no-code database builder platform, allowing users to perform various data operations on their Ragic forms via HTTP API. It supports reading multiple or single records, creating new records, updating existing ones, and retrieving files stored in Ragic.
Common scenarios include:
- Automating data retrieval from Ragic databases for reporting or further processing.
- Creating or updating records in Ragic based on external triggers or workflows.
- Downloading files stored in Ragic records for use in other systems.
Practical examples:
- Fetching a list of customer records with filters applied.
- Updating a specific record's fields after receiving updated information.
- Uploading new entries with complex subtable data.
- Downloading an image file attached to a Ragic record.
Properties
| Name | Meaning |
|---|---|
| Action | The operation to perform: - Read Data - Read Single Data - Create New Data - Update Existed Data - Retrieve File |
| Method | (For create/update actions) Choose how to send data: - JSON - Field (individual field entries) |
| Form | The Ragic form to operate on. Only forms where the user is admin are listed. Can also specify by ID using expressions. |
| Record Index | (For update and read single data) The index of the record to target, found in the record URL. |
| JSON Body | (For create/update with JSON method) The JSON payload representing the record data according to Ragic API format. |
| Entries | (For create/update with Field method) Collection of field entries specifying field, content type (text/file), and value. |
| Subtable Entries | (For create/update with Field method) Collection of subtable entries specifying subtable record node ID, subtable field, content type, and value. |
| Show Subtables | (For read actions) Whether to include subtable data in the response. |
| Ignore Masked | (For read actions) Whether to show unmasked values of "Masked text" fields. |
| Limit | (For read data) Maximum number of records to return. Setting too high may cause timeouts. |
| Filters | (For read data) Conditions to filter returned records. Each filter includes field, operand (e.g., equals, greater than), and condition value. |
| Other Parameters | Additional query parameters to include in the API request. |
| File Download With User Authentication | (For retrieve file) Whether the company setting "File Download With User Authentication" is enabled. |
| Account Name | (For retrieve file without user authentication) The account name where the file is located. |
| File Record Url | (For retrieve file with user authentication) The URL of the record containing the file. |
| File Name | (For retrieve file) The exact file name to download, as obtained from a previous read action. |
Output
- For data read or write actions, the output is a JSON array representing the API response from Ragic. This typically contains record data, including subtables if requested.
- For file retrieval, the output includes binary data under the
binaryproperty nameddownloadedFile, along with metadata such as filename and MIME type. This allows downstream nodes to handle the file appropriately.
Dependencies
- Requires an API key credential for authenticating with the Ragic HTTP API.
- Needs network access to the Ragic server specified in the credentials.
- Uses Ragic's documented HTTP API endpoints for all operations.
- No additional external libraries beyond n8n core helpers are required.
Troubleshooting
- Failed to parse API response as JSON: This error occurs if the response from Ragic is not valid JSON. Check network connectivity, API key validity, and that the requested resource exists.
- Timeouts when reading large datasets: Setting the "Limit" property too high can cause API timeouts. Reduce the limit or apply filters to narrow results.
- Invalid Record Index: When updating or reading a single record, ensure the correct record index is provided as per the URL structure.
- File download issues: If downloading files fails, verify whether "File Download With User Authentication" is enabled in company settings and provide the appropriate parameters accordingly.
- Field or Subtable field options not loading: Ensure credentials are valid and the selected form exists and is accessible.