FileMaker and Sierra Interactive integration

Make sure you have n8n installed and running:

• Install n8n on any platform using npm or Docker;
• Or let n8n host it for you on its cloud infrastructure.

In n8n, click the "Add workflow" button in the Workflows tab to create a new workflow.

Add the starting point – a trigger on when your workflow should run: on an app event, on schedule, on a webhook call, when called by another workflow, or manually. In some cases, the HTTP Request node might already serve as your starting point.

Drag the FileMaker node from the nodes panel on the left to the workflow canvas. Before dragging, choose the action FileMaker will perform. You can also swap steps and add the Sierra Interactive node first, as the step 4.

Click on the FileMaker node, then click on the "Select credential" dropdown option next to the “Credential to connect with” field. Follow the authentication process to grant n8n access to your FileMaker. You can also share credentials you've created, and store sensitive credential information in an external vault using n8n's external secrets feature.

Add the HTTP Request node to your workflow canvas and authenticate it using a predefined credential type. This allows you to perform custom operations, without additional authentication setup.

Click on the HTTP node to configure its settings. With generic authentication, you'll typically need to provide endpoint URLs, headers, parameters, and any other authentication details specific to the service you're integrating with:

• Find the documentation of the Sierra Interactive API and see if the API supports HTTP requests;
• Most APIs require some form of authentication and you can configure this in the HTTP Request mode (Basic Auth, Custom Auth, Digest Auth, Header Auth, OAuth1 API, OAuth2 API, Query Auth).

Connect the output of the Sierra Interactive node to the input of the FileMaker node or vice versa.