Filemaker Node perform Script output

Questions
1

HI all, is there a way to read the script output of a Filemaker node after “perform script” action? At the moment i get the info about the successful execution of the script, but not the data my Filemaker-script returns.

2 Likes
2

Hey @VolkerBT,
Welcome to the community!

yes, you can get the script’s returned data, but only if the script actually returns something in a way the FileMaker Data API exposes. In FileMaker, the Data API only returnes a “script result” when your script ends with Exit Script and you set a Text Result (that value becomes scriptResult in the API response).

you should update your FileMaker script to end with Exit Script [ Text Result: JSON… ] (or whatever string you want back), then in n8n check the output of the FileMaker node for response.scriptResult (or similar) and map that into your next node. If the n8n FileMaker “Perform Script” node still doesn’t surface it cleanly, the reliable workaround is to call the FileMaker Data API directly with an HTTP Request node and parse response.scriptResult from the JSON response yourself.

2 Likes
3

Hi @VolkerBT Welcome to the community!
For now with the latest stable version the filemaker node is not actually exposed to much customization so i would say you currently cannot do that.

1 Like
4

Hi @VolkerBT — welcome to the n8n community :waving_hand:
I agree with @Anshul_Namdev,
There are a few approaches you can try depending on how your FileMaker solution is structured:

1st: Store the Script Output in a Field

Instead of returning data only as a script result, the FileMaker script can write the output into a table field.
to do so:

In your FileMaker script

  1. Run your logic.
  2. Save the result into a field (for example api_result).
  3. Commit the record.
    Example:
Set Field [ Table::api_result ; JSON result ]
Commit Records/Requests

In n8n

After Perform Script, add a Get Record(s) node and read that field.

2nd: Call the FileMaker Data API with an HTTP Request Node you

can call the Data API directly using an HTTP Request node.

3rd: Use an Intermediate Record or Parameter Table

let the script write its output to a known record or helper table, which n8n reads afterward

Let us know how your worked is structured if you’d like more specific suggestions :slightly_smiling_face:

5

thank you all for your replies! Sice i am a lazy guy i will just write the script output into a fileld and read it from ther

6

Yes @VolkerBT you can retrieve script output from FileMaker when using the “Perform Script” action, but it requires specific configuration on both the FileMaker and n8n sides.

Your FileMaker script needs to explicitly return data using the Exit Script step:

Exit Script [ Result: YourDataHere ]

The result can be:

  • Plain text

  • JSON (recommended for structured data)

  • XML

  • Any string value

In your FileMaker node:

  • Operation: Perform Script

  • Script Name: Your script name

  • Script Parameter: (optional) Data to pass to the script

  • Return Fields: Make sure this is configured if available

The script result should appear in the node output under a field like:

  • scriptResult

  • response

  • Or in the main JSON output

You can then use an Expression in subsequent nodes:

{{ $json.scriptResult }}