Home / Blog / Claris Connect Use-case: Web Input for Your FileMaker Apps

Claris Connect Use-case: Web Input for Your FileMaker Apps

Here’s a scenario: You have a FileMaker app, but once in a while, you need to capture input through the web from a wide variety of folks. Those users will not have the FileMaker Pro or Go client; they would be expected to use their browser. FileMaker WebDirect would be the obvious choice since it requires no prior knowledge of HTML or CSS or JavaScript to create an actual web page to allow this interaction.

Like the Pro and Go client software, WebDirect expects users to log in, however. If you want people to just go to a page and input some data, you have to jump through a few hoops to create a new FileMaker file and set it to auto-login and then very carefully craft the associated privilege set so that it does not accidentally expose more data and functionality than you intend. And for this particular effort, you do not want to create an actual account for each of those users and deal with all the maintenance that comes with that. WebDirect is not always a natural choice for this kind of anonymous access.

With Claris Connect, you now have a new way of tacking this use case. Claris Connect has built-in connectors for three online form providers:

FIgure 1. Screenshot of icons for Typeform, Formstack, Wufoo online form providers
Figure 1. Online form providers

Each of them offers a single trigger: to start a flow when a form is submitted:

Form 2. Screenshot of trigger to start a flow
Figure 2. Trigger to start a flow

For this example, a simple poll from Typeform’s arsenal of templates will do. In Typeform, select the ‘funny online poll template.’

Figure 3. Screenshot pointing to the Funny Online Poll Template
Figure 3. Select the “Funny Online Poll Template”

Back to Claris Connect, start a new flow and select Typeform as the trigger, authenticate to their service and accept the permissions that Claris Connect requires.

Figure 4. Screenshot of the permissions and Accept or Cancel buttons
Figure 4. Accept the permissions

Next, you can select the Poll you just created:

Figure 5. Screenshot of selecting poll that was created
Figure 5. Select the poll

At this point, Claris Connect will ask you to submit the chosen form so that it can learn what to expect, and also so that you can then use that sample response in the next actions that you will add to the flow.

Go to Typeform and copy the URL for your form:

Figure 6. Screenshot of pointing to the URL in the Share your typeform field
Figure 6. Copy the URL

And use that URL in a new browser tab, make a selection and submit the form.

Figure 7. Screenshot of URL loaded in browser
Figure 7. URL loaded in the browser

Claris Connect will indicate that the form submission was received.

Figure 8. Screenshot of the form sucessfully submitted
Figure 8. Form submission completed

As the next action in the flow, select the FileMaker connector that fits your deployment: regular FileMaker Server, FileMaker Cloud, or an on-premise agent, and choose the ‘Create Record’ event.

FIgure 9. Screenshot of selecting a FileMaker connector and choosing Create Record
Figure 9. Select the FileMaker connector and choose “Create Record”

Claris Connect will show you any existing connections you may have already. A connection encompasses a particular FileMaker server, file, and account, and the one listed is not for the file that I want to use for this.

Figure 10. Screenshot of existing connections
Figure 10. Existing connection(s)

Click on ‘Connect New Account’ and fill in the DNS name of your FileMaker Server, the name of the FileMaker file that has the layout you want to interact with and the credentials to use:

Figure 11. Screenshot of connecting an account. Provide the doman, username, password, and DNS name of your FileMaker Server
Figure 11. Specify DNS name of your FileMaker Server

Sign in to confirm that all the settings are correct, and your new connection will show up in the list. Make sure to rename it to something meaningful to distinguish it from the other connections. I use the name of the server and the name of the file.

Figure 12. Screenshot of new connection added to the list
Figure 12. New connection added to the list

With the new connection selected, you can continue with the rest of the configuration. The next step in the action is to select the layout that will be used to create this new record.

Figure 13. Screenshot of selecting the layout to be used
Figure 13. Select layout to be used

Claris Connect will show all the fields on that layout so that we can pick from the Typeform poll’s data what needs to go where.

For the ‘answer’ field, pick the first response:

Figure 14. Screenshot of fields on the layout
Figure 14. Fields on the layout

And for the ‘type_form_data’ field select the form_response node:

Figure 15. Screenshot of details for the type_form_data field
Figure 15. Select the “form_response” node

Save the settings and enable the flow:

Figure 16. Screenshot of saving the settings and the Enabled button turned on for the flow
Figure 16. Turn the “Enabled” button on

In your browser, bring up the form again and submit a new response. In the FileMaker file you will now see a new record with the data from your form:

Figure 17. Screenshot of the submitted response added as a new record in FileMaker
Figure 17. New record created in the FileMaker file

Since you selected the full response node to go into the ‘type_form_data’ field, you now have all of the form’s JSON that you can parse further if you need to.

You can add an action to your flow to execute your FileMaker script, for instance, to do that parsing.

Figure 18. Screenshot of selecting an action to add to the flow
Figure 18. Adding an action to execute your FileMaker script

With this flow, you now have the ability to share the Typeform URL and have data flow into your FileMaker solution.

Some of the benefits using these types of flows to enable web input to your FileMaker solution

  • Much like WebDirect, you do not need any web coding skills to create and set up the form
  • The infrastructure is not yours; you do not need to worry if 100 users decide to submit the form at the same time. Both TypeForm and Claris Connect take care of handling that load. With WebDirect, your server would need to be able to handle the 100 actual client sessions, which are much more taxing on your server’s resources than the few Data API connections that Claris Connect uses.
  • If you do not want your FileMaker Server to be exposed to the internet at all you can use the Claris Connect on-premise agent to act as the gateway (see our blog post about the on-premise agent)


It actually took me much longer to write all of this up than to set up and configure this flow. Form builders like the ones supported by Claris Connect are an easy and scalable way to allow efficient web input for your FileMaker solutions. Or your MySQL solutions for that matter, the flow data can just as easily flow to the MySQL connector.

And here’s a thought: while not covered by Claris Connect connectors, you could actually build the form using the Typeform APIs from inside FM…

1 thought on “Claris Connect Use-case: Web Input for Your FileMaker Apps”

Leave a Comment

Your email address will not be published. Required fields are marked *