FileMaker OttoFMS icon

FileMaker OttoFMS

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

Actions7

Overview

This node allows users to execute FileMaker scripts via the OttoFMS DataAPI Proxy. It is designed to run a specified FileMaker script by name, optionally passing parameters to it, and retrieving the result. This is useful in scenarios where automation or integration workflows need to trigger backend logic defined in FileMaker scripts, such as data processing, validation, or custom business rules.

Practical examples include:

  • Running a FileMaker script that generates a report and returns the results.
  • Triggering a script that updates records based on input parameters.
  • Executing complex calculations or workflows encapsulated in FileMaker scripts from an external automation platform.

Properties

Name Meaning
Script Name The exact name of the FileMaker script to execute (case-sensitive).
Script Parameter Optional parameter to pass to the script; can be a JSON string or plain text.
Timeout (Ms) Maximum time in milliseconds to wait for the script execution response before timing out.
Parse JSON Result Whether to attempt parsing the script's returned result as JSON if possible (true/false).

Output

The node outputs the result of the executed FileMaker script in the json field of the output data. If the "Parse JSON Result" option is enabled and the script returns valid JSON, the output will be parsed into structured JSON objects. Otherwise, the raw string result is provided.

No binary data output is indicated by the source code or properties.

Dependencies

  • Requires an API key credential for authenticating with the OttoFMS DataAPI Proxy service.
  • The node depends on the OttoFMS DataAPI Proxy endpoint to communicate with FileMaker Server.
  • Proper configuration of the API credentials and network access to the proxy service is necessary.

Troubleshooting

  • Timeouts: If the script takes longer than the configured timeout, the request will fail. Increase the "Timeout (Ms)" value if needed.
  • Script Not Found: Providing an incorrect or misspelled script name will cause errors. Ensure the script name matches exactly, including case sensitivity.
  • Invalid Script Parameter: Passing malformed JSON or unsupported parameter formats may cause the script to fail or return unexpected results.
  • JSON Parsing Errors: If "Parse JSON Result" is enabled but the script returns non-JSON text, parsing will fail. Disable this option or ensure the script returns valid JSON.
  • Authentication Failures: Incorrect or missing API credentials will prevent communication with the proxy service.

Links and References

Discussion