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" provides integration with FileMaker databases via the OttoFMS DataAPI Proxy. Specifically, for the Record - Update operation, it allows users to update an existing record in a specified FileMaker table by providing the primary key of the record and the new data fields to be updated.

This node is beneficial when you need to programmatically modify records in a FileMaker database as part of an automated workflow. For example, updating customer information after receiving new data from a CRM system or modifying inventory details based on stock changes.

Properties

Name Meaning
Table Name The name of the FileMaker table (Table Occurrence) where the record exists and will be updated.
Primary Key The unique identifier value of the record to update (e.g., "123" or "ABC-456").
Record Data JSON object containing field names as keys and their new values to update in the record.

Example of Record Data JSON:

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

Output

The node outputs JSON data representing the result of the update operation. Typically, this includes confirmation that the record was updated successfully along with any metadata returned by the FileMaker API, such as the updated record's ID or modification timestamp.

If the node supports binary data output (not indicated here), it would represent file attachments or media related to the record, but for this operation, the output is primarily JSON reflecting the updated record state.

Dependencies

  • Requires connection to a FileMaker server accessible via the OttoFMS DataAPI Proxy.
  • Needs an API authentication token or API key credential configured in n8n to authorize requests.
  • The user must have appropriate permissions to update records in the specified FileMaker table.

Troubleshooting

  • Invalid Primary Key: If the provided primary key does not exist, the update will fail. Verify the key value matches an existing record.
  • Malformed JSON in Record Data: Ensure the JSON object for record data is correctly formatted and uses valid field names as defined in the FileMaker schema.
  • Permission Denied: Insufficient permissions on the FileMaker server can cause errors. Confirm the API credentials have update rights.
  • Network or API Errors: Connectivity issues or incorrect API endpoint configuration may lead to request failures. Check network access and proxy settings.

Common error messages might include:

  • "Record not found" — means the primary key does not match any record.
  • "Unauthorized" or "Forbidden" — indicates credential or permission problems.
  • "Invalid JSON" — points to syntax errors in the record data input.

Resolving these typically involves verifying inputs, credentials, and server accessibility.

Links and References

Discussion