# Extract FileMaker Contact Fields

Source: https://openflow.run/en/templates/extract-filemaker-contact-fields/
Content language: en
Template revision: 6a810ce0d6451572951d8ffad4656467a01774f0

Productivity

Extract each fieldData object from a FileMaker Data API response.

[Use in Open Flow](https://console.openflow.run/flows?importUrl=https%3A%2F%2Fraw.githubusercontent.com%2Foomol-lab%2Fawesome-workflow-templates%2F6a810ce0d6451572951d8ffad4656467a01774f0%2Fworkflows%2Fextract-filemaker-contact-fields%2Ftemplates%2Fextract-filemaker-contact-fields.openflow.json)

*   [Open Flow JSON](https://github.com/oomol-lab/awesome-workflow-templates/blob/6a810ce0d6451572951d8ffad4656467a01774f0/workflows/extract-filemaker-contact-fields/templates/extract-filemaker-contact-fields.openflow.json)
*   [n8n JSON](https://github.com/oomol-lab/awesome-workflow-templates/blob/6a810ce0d6451572951d8ffad4656467a01774f0/workflows/extract-filemaker-contact-fields/templates/extract-filemaker-contact-fields.n8n.json)

![Extract FileMaker Contact Fields workflow in Open Flow](https://openflow.run/template-previews/extract-filemaker-contact-fields/light.webp)

Extract each fieldData object from a FileMaker Data API response.

## Setup and use

Supply a FileMaker Data API response object to Open Flow.

## Behavior

Each entry in response.data contributes its complete fieldData object. Open Flow returns an array. Record metadata and portal data are not included. This example does not fetch further FileMaker pages.

In n8n

In n8n run the manual workflow with its fictional example response, or replace that example with your own response. N8n emits an item for each record.

Inspiration & credits

## Changes to the source

*   Replace the original contact sample with fictional records and add a manual trigger. Open Flow accepts the response as input.

Adapted from [Extract FileMaker response records](https://github.com/Zie619/n8n-workflows/blob/ae8cf6dc5b873cbb4f74587aa9180ed3a9f70682/workflows/Functionitem/0184_Functionitem_Itemlists_Automate.json) in [Zie619/n8n-workflows](https://github.com/Zie619/n8n-workflows). The source export does not identify a separate template author or license.

The collection’s [MIT notice](https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/LICENSE) is pinned at a later revision. This is the collection notice at that revision; it does not establish a separate original template author’s license. Our changes are listed above; see [repository licensing](https://github.com/oomol-lab/awesome-workflow-templates/blob/6a810ce0d6451572951d8ffad4656467a01774f0/README.md#licensing).

> MIT License
> 
> Copyright (c) 2025 Zie619
> 
> Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
> 
> The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
> 
> THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

## What you’ll need

*   A FileMaker Data API response object

*   filemaker
*   contacts
*   data

[View on GitHub](https://github.com/oomol-lab/awesome-workflow-templates/blob/6a810ce0d6451572951d8ffad4656467a01774f0/workflows/extract-filemaker-contact-fields/README.md)
