Zapier with Umbraco Forms
Details an integration available for Zapier with Umbraco Forms, built and maintained by Umbraco HQ.
Last updated
Details an integration available for Zapier with Umbraco Forms, built and maintained by Umbraco HQ.
Last updated
This integration is an add-on to the Zapier CMS integration and provides necessary components for handling form submissions based on the registered subscription hooks.
A Zap is an automated workflow that connects apps and services together. Each Zap consists of a trigger and one or more actions.
Major | Minor/Patch |
---|---|
Major | Minor/Patch |
---|---|
Version 4.0.0
of the integration adds some breaking changes to the Zaps creation flow with the new API endpoints and the Web Components-based Umbraco backoffice.
As a result, users on Umbraco 14+ will need to use version 3.0.0
of the Umbraco Zapier application.
Version 3.0.0
of the Umbraco app is available in the Zapier marketplace via the following invitation: https://zapier.com/developer/public-invite/157905/5f6dc86efe92c244cf0b2ff62af9d747/
Zapier allows only one version of the application to be public. Because the current version is used by instances running Umbraco <= 13, the latest version can be installed through the invite URL above.
For this integration, the authentication is managed on Zapier's side by using the Umbraco Marketplace app.
The Umbraco app manages two types of events:
New Form Submission - triggers when a form is submitted.
New Content Published - triggers when new content has been published.
The trigger event to be used by this integration is New Form Submission.
When creating the Zap trigger, you will be prompted to enter a username, password, and URL for your Umbraco website.
It is also possible to use an API key. If the following setting is present, the API key-based authentication will take precedence and will be used for authorization.
If no API key is present, the Umbraco application will validate the credentials entered and return a message in case the validation fails.
To enhance security, you can specify a User Group that the user connecting needs to be a part of. This can be achieved by adding the following setting to the configuration file:
Version 8
8.1.0
Version 10
10.1.0
Version 11
11.0.0
Version 8
8.9.1
Version 10
10.1.0
Version 11
11.0.0