Connect to YepCode on Zapier
YepCode uses session authentication to authenticate your account on Zapier.
Required authentication fields
YepCode account:
- Email address
- Password
- Team identifier
Optional authentication fields
- None
Additional authentication instructions
Your YepCode team identifier is the token found after logging into your account. Learn more about authenticating your YepCode account in Zapier.
About YepCode's app
| Are self-hosted or cloud-hosted accounts supported? | Cloud-hosted accounts only | |
| Is a paid YepCode plan required? | No | View YepCode's plans. |
| Are any special account permissions required? | No | |
| Are there usage limits? | Yes | Usage limits are based on your YepCode pricing plan. |
| Are there pagination limits? | Yes |
The YepCode app will display the first 100 YepCode processes that have webhooks enabled. The app will not display processes that do not have webhooks enabled. |
| Do trigger samples use real data from your account or generic data? | Not applicable | |
| Are custom fields supported? | No | |
| Do update actions overwrite or append to existing data? | Depends | It depends on the business logic that you implemented in YepCode. Learn more about YepCode's update actions. |
| Is there any additional info? | No |
