Skip to content

Commit 0ef0efb

Browse files
authored
Update readme.md
1 parent 0c7660b commit 0ef0efb

File tree

1 file changed

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

1 file changed

+9
-3
lines changed

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

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

1616
### Authentication
1717

18-
For this integration, the authentication is managed on Zapier's side.
18+
For this integration, the authentication is managed on Zapier's side by using the Umbraco marketplace app.
1919

20-
When creating a Zap trigger, you will be prompted to enter a username, password and the URL for your Umbraco website.
20+
The Umbraco app manages two types of events:
21+
* New Form Submission - triggers when a form is submitted
22+
* New Content Published - triggers when a new content has been published.
2123

22-
Then the Umbraco application existing in the Zapier marketplace will validate the credentials entered and return a message in case the validation fails.
24+
The trigger event to be used by this integration is _New Form Submission_.
25+
26+
When creating the Zap trigger, you will be prompted to enter a username, password and the URL for your Umbraco website.
27+
28+
Then the Umbraco application will validate the credentials entered and return a message in case the validation fails.
2329

2430
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
2531
setting in `Web.config`:

0 commit comments

Comments
 (0)