Skip to content

Commit cf9c2a7

Browse files
authored
Update readme.md
1 parent 0f38f60 commit cf9c2a7

File tree

1 file changed

+9
-3
lines changed
  • src/Umbraco.Cms.Integrations.Automation.Zapier

1 file changed

+9
-3
lines changed

src/Umbraco.Cms.Integrations.Automation.Zapier/readme.md

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,11 +18,17 @@ Requires minimum versions of Umbraco:
1818

1919
### Authentication
2020

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.
2222

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.
2426

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.
2632

2733
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
2834
setting in `Web.config`:

0 commit comments

Comments
 (0)