- If you are using Terraform to configure a custom email provider, delete your existing Auth0 tenant custom email provider.
- Auth0 has a maximum limit of one Action for Actions associated with the following triggers: custom-phone-provider and custom-email-provider.
- Create an
auth0_action
:
In order to bind a Terraform
auth0_action
to an auth0_trigger_action
, set the auth0_action to deploy = true
. To learn more, read Terraform’s auth0_action documentation.- Bind the
auth0_action
to the custom-email-providerauth0_trigger_action
:
- Configure the
auth0_email_provider
resource to use theauth0_action
:
Troubleshoot
Scenario: Custom email provider configured using Terraform is not taking effect, and the displays a different Action. You may have multiple custom provider Actions withdeploy: true
. Auth0 has a maximum limit of one Action for Actions associated with the following triggers: custom-phone-provider
and custom-email-provider
.
- If you encounter this scenario, it’s recommended that you list your Actions to identify any duplicates to delete.
- If you encounter this scenario after managing your custom providers through multiple methods (Terraform, Auth0 Dashboard, , and/or Auth0 SDKs) it is advisable to reset the custom provider configuration. We recommend you refrain from using multiple methods to manage your custom provider.