You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/Umbraco.Cms.Integrations.Automation.Zapier/readme.md
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,11 +18,17 @@ Requires minimum versions of Umbraco:
18
18
19
19
### Authentication
20
20
21
-
For this integration, the authentication is managed on Zapier's side.
21
+
For this integration, the authentication is managed on Zapier's side by using the Umbraco marketplace app.
22
22
23
-
When creating a Zap trigger, you will be prompted to enter a username, password and the URL for your Umbraco website.
23
+
The Umbraco app manages two types of events:
24
+
* New form submission - triggers when a form is submitted
25
+
* New Content Published - triggers when a new content has been published.
24
26
25
-
Then the Umbraco application existing in the Zapier marketplace will validate the credentials entered and return a message in case the validation fails.
27
+
The trigger event to be used by this integration is _New Content Published_.
28
+
29
+
When creating the Zap trigger, you will be prompted to enter a username, password and the URL for your Umbraco website.
30
+
31
+
Then the Umbraco application will validate the credentials entered and return a message in case the validation fails.
26
32
27
33
If you want to extend the security layer, you can also specify a user group that the user trying to connect needs to be a part of, by adding the following
0 commit comments