FileMaker OttoFMS icon

FileMaker OttoFMS

Execute FileMaker scripts, request data, and manage data via OttoFMS DataAPI Proxy
Join our community

Actions7

Overview

The node "FileMaker OttoFMS" enables interaction with FileMaker databases through the OttoFMS DataAPI Proxy. Specifically, for the Record - Get operation, it retrieves records from a specified FileMaker table (Table Occurrence) based on optional query parameters such as filtering, sorting, selecting specific fields, and pagination controls.

This node is beneficial when you need to programmatically fetch data from FileMaker tables within an n8n workflow, for example:

  • Retrieving customer records filtered by certain criteria (e.g., customers older than 25).
  • Fetching a sorted list of records for reporting or further processing.
  • Selecting only specific fields to reduce payload size and improve performance.
  • Implementing pagination by skipping a number of records and limiting the total returned.

Properties

Name Meaning
Table Name The name of the FileMaker table (Table Occurrence) from which to retrieve records.
Query Options Collection of optional parameters to refine the query:
  Filter! OData filter expression to select records matching conditions (e.g., Name eq 'John' or Age gt 25).
  Order By Field name to sort the results by, with optional direction (e.g., Name asc, CreatedDate desc).
  Select Fields Comma-separated list of fields to return (e.g., Name,Email,Phone).
  Skip (Offset) Number of records to skip before starting to return results (for pagination).
  Top (Limit) Maximum number of records to return (limit the result set size).

Output

The node outputs JSON data representing the retrieved records from the specified FileMaker table. Each item in the output corresponds to a record matching the query parameters. The structure typically includes field names as keys and their corresponding values.

If the node supports binary data output (not explicitly shown here), it would represent file attachments or media stored in FileMaker fields, but this is not detailed in the provided code snippet.

Dependencies

  • Requires connection to a FileMaker server accessible via the OttoFMS DataAPI Proxy.
  • Needs an API authentication credential configured in n8n to authorize requests to the FileMaker OttoFMS service.
  • The node sends and receives data in JSON format over HTTP with appropriate headers (Content-Type: application/json and Accept: application/json).

Troubleshooting

  • Common Issues:

    • Incorrect table name: Ensure the "Table Name" matches exactly the FileMaker Table Occurrence.
    • Invalid filter syntax: The filter must be a valid OData expression; otherwise, the request may fail or return no results.
    • Exceeding limits: Setting very high "Top" values might cause performance issues or timeouts.
    • Authentication errors: Verify that the API key or credentials are correctly configured and have sufficient permissions.

  • Error Messages:

    • Authorization failures usually indicate invalid or missing API credentials.
    • Syntax errors in filter or orderby expressions will result in API errors; review and correct the expressions.
    • Network or connectivity errors suggest issues reaching the FileMaker OttoFMS proxy endpoint.

Links and References

  • OData Filter Query Syntax
  • FileMaker official documentation for Table Occurrences and Data API usage (refer to your FileMaker version's docs)
  • OttoFMS DataAPI Proxy documentation (if available internally or from the provider)

This summary is based solely on static analysis of the provided source and property definitions without runtime execution.

Discussion