FileMaker OttoFMSInstall

Overview

The node "FileMaker OttoFMS" enables interaction with FileMaker databases through the OttoFMS DataAPI Proxy. Specifically, for the Record - Create operation, it allows users to create new records in a specified FileMaker table by sending JSON-formatted data representing the record fields and their values.

This node is beneficial when automating workflows that require adding new entries to FileMaker databases without manual input. For example, it can be used to automatically log form submissions, add customer information from an external system, or insert transaction records triggered by other events in an automation pipeline.

Properties

Example of Record Data:

{
  "FirstName": "John",
  "LastName": "Doe",
  "Email": "john.doe@example.com"
}

Output

The node outputs JSON data representing the result of the create operation. This typically includes details about the newly created record such as its unique record ID and any metadata returned by the FileMaker API proxy.

If the node supports binary data output, it would represent file attachments or container fields stored in FileMaker, but based on the provided code and properties, the primary output is JSON structured data reflecting the created record.

Dependencies

• Requires an API key credential for authenticating with the OttoFMS DataAPI Proxy.
• The node depends on the OttoFMS DataAPI Proxy service to communicate with FileMaker databases.
• Proper configuration of the FileMaker database and tables is necessary to ensure the table names and field names match those used in the node properties.

Troubleshooting

• Common issues:

  • Incorrect table name or field names may cause errors or failed record creation.
  • Malformed JSON in the Record Data property can lead to request failures.
  • Authentication errors if the API key credential is missing or invalid.
  • Network or proxy connectivity issues between n8n and the OttoFMS DataAPI Proxy.

• Error messages and resolutions:

  • "Invalid table name" — Verify the exact spelling and case of the FileMaker table name.
  • "Field not found" — Ensure all field names in the JSON match those defined in the FileMaker schema.
  • "Authentication failed" — Check that the API key credential is correctly configured and has proper permissions.
  • "Malformed JSON" — Validate the JSON syntax in the Record Data input.

Links and References

• FileMaker Official Documentation
• OttoFMS DataAPI Proxy Documentation
• n8n Documentation on Creating Custom Nodes