FILEMAKER n8n INTEGRATION: AUTOMATE FILEMAKER WITH N8N

The Create Record action lets you add new records to any FileMaker layout directly from your n8n workflows. This is fundamental for building integrations that push data into FileMaker from external sources—web forms, other databases, APIs, or any application connected to n8n.

Key parameters:

• Credential to connect with: A dropdown selector where you choose your pre-configured FileMaker account credentials. This is required to authenticate the connection.
• Layout Name or ID: Specify the target layout in FileMaker where the new record will be created. This field accepts text input and is required since records are always created within a specific layout context.
• Fields: Define which fields to populate and their values when creating the record. You can add multiple fields, each accepting a field name and value (fixed or expression). This is where you map incoming data to your FileMaker field structure.

Typical use cases:

• Create new customer records when leads fill out contact forms
• Add inventory items from e-commerce platforms automatically
• Generate project records when tasks are created in project management tools
• Log webhook events as records for audit purposes

The Get Records action retrieves multiple records from a specified FileMaker layout with pagination control. It's your go-to action for pulling batches of data from FileMaker into your workflows for processing, transformation, or synchronization with other systems.

Key parameters:

• Credential to connect with: Select your FileMaker account credentials from the dropdown. Required.
• Layout Name or ID: Specify the layout from which to retrieve records. Required.
• Offset: A numeric value defining the starting record index. Set to 1 to start from the first record. Useful for paginating through large datasets.
• Limit: Controls how many records to fetch in this action, accepting values like 100 to cap results. Required.
• Get Portals: Toggle to enable retrieval of related portal data from the layout. Off by default.
• Sort Data?: Enable to sort returned records based on specified criteria.
• Script toggles: Three optional toggles (Before Find Script, Before Sort Script, After Sort Script) allow executing FileMaker scripts at specific points during retrieval.

When to use it: Perfect for batch exports, data synchronization jobs, generating reports, or any scenario where you need to process multiple records. Combine with the offset and limit parameters to handle large datasets in manageable chunks.

This action retrieves a specific record using its unique record ID. When you know exactly which record you need, this is more efficient than running a find query—it goes straight to the target.

Key parameters:

• Credential to connect with: Your FileMaker account credentials. Required.
• Layout Name or ID: The layout containing the record. Required.
• Record ID: The unique numeric identifier of the record to retrieve. Required.
• Get Portals: Toggle to fetch related portal records alongside the main record. Optional, off by default.
• Sort Data?: Enable sorting of results if needed.
• Script toggles: Execute custom FileMaker scripts before find, before sort, or after sort operations.

Typical use cases:

• Fetch customer details after receiving a webhook with a customer ID
• Retrieve order information for processing or display
• Pull specific record data to include in automated notifications

The Find Records action performs advanced searches across your FileMaker data using configurable queries. This mirrors FileMaker's native find functionality, letting you locate records matching specific criteria.

Key parameters:

• Credential to connect with: Select FileMaker credentials. Required.
• Layout Name or ID: The layout to search within. Required.
• Offset: Starting point for pagination (default: 1).
• Limit: Maximum records to return (default: 100).
• Get Portals: Toggle to include related portal data in results.
• Response Layout Name or ID: Customize the response format using a different layout.
• Queries: Add one or more query conditions to filter records. Each query specifies field criteria that records must match.
• Sort Data?: Enable to sort the found records.

Practical applications:

• Find all orders with "pending" status for processing
• Locate customers in a specific region for targeted campaigns
• Search for records modified within a date range
• Filter products by category or inventory level

This action shines when you need to retrieve subsets of data based on dynamic conditions passed from other nodes in your workflow.

The Edit Record action updates existing records in FileMaker by specifying the record ID and the fields to modify. It's essential for keeping your FileMaker data synchronized with external systems.

Key parameters:

• Credential to connect with: Your FileMaker account credentials. Required.
• Layout Name or ID: The layout containing the record to edit. Required.
• Record ID: The unique identifier of the record to modify. Required.
• Mod ID: The modification ID for concurrency control—FileMaker uses this to prevent conflicting updates when multiple users or processes access the same record.
• Fields: Specify which fields to update and their new values. Add multiple fields as needed. This is where you define exactly what changes to make.

Use cases:

• Update customer information when they modify their profile elsewhere
• Change order status based on shipping notifications
• Sync inventory levels from e-commerce platforms
• Update record timestamps or modification logs automatically

💡 Pro tip: The Mod ID parameter helps prevent data conflicts. If another process modified the record since you last retrieved it, the edit will fail, protecting data integrity.

The Delete Record action removes a specific record from FileMaker using its record ID. Use this carefully—deleted records cannot be recovered through the API.

Key parameters:

• Credential to connect with: Your pre-configured FileMaker credentials. Required.
• Layout Name or ID: The layout containing the record to delete. Required.
• Record ID: The unique identifier of the record to remove. Required.

When to use it:

• Clean up test records automatically
• Remove canceled orders or archived entries
• Delete duplicate records identified through find operations
• Maintain data hygiene by removing outdated entries based on business rules

Always implement safeguards in your workflows when using delete actions—consider logging deletions or requiring confirmation for sensitive data.

The Duplicate Record action creates a copy of an existing record, preserving its field values while generating a new record ID. This is useful for templating or creating variations of existing entries.

Key parameters:

• Credential to connect with: FileMaker account credentials. Required.
• Layout Name or ID: The layout containing the source record. Required.
• Record ID: The unique identifier of the record to duplicate. Required.

Practical scenarios:

• Create template-based records for recurring projects
• Duplicate product records when creating variations
• Copy customer profiles for related contacts
• Generate recurring entries based on existing templates

After duplication, you can chain an Edit Record action to modify specific fields on the new copy, creating a powerful pattern for template-based record generation.

The Perform Script action executes FileMaker scripts directly from your n8n workflows, unlocking the full power of your existing FileMaker business logic within automated processes.

Key parameters:

• Credential to connect with: Your FileMaker credentials. Required.
• Layout Name or ID: The layout context for script execution. Required depending on the script's needs.
• Script Name or ID: The name or ID of the FileMaker script to run. Required.
• Script Parameter: Pass parameters or arguments to the script during execution. This accepts free text and is optional—depends on whether your script expects input.

Use cases:

• Trigger complex FileMaker business logic from external events
• Run data validation or transformation scripts before exports
• Execute cleanup or maintenance scripts on schedule
• Call scripts that interact with FileMaker-specific features not directly available through the API

This action is particularly valuable when you've invested in sophisticated FileMaker scripts and want to leverage them within broader automation workflows. Need expert help building complex automations? Our n8n agency can assist with your integration projects.