-
**Why**
To be able to give better answers why a message was not sent to a subscriber we need to get some info from the provider with a webhook. (deliverability status, rejection status etc).
**How**…
-
**Why**
To be able to give better answers why a message was not sent to a subscriber we need to get some info from the provider with a webhook. (deliverability status, rejection status etc).
**How**…
-
**Why?**
Currently, when the user connects a provider from the Integration store, there's no option to `Test the provider connection` before saving/updating it for wrong/bad credentials or other poss…
-
## Why?
Currently, when the user connects a provider from the Integration store, there's no option to `Test the provider connection` before saving/updating it for wrong/bad credentials or other possi…
-
## Why?
Currently, when the user connects a provider from the Integration store, there's no option to `Test the provider connection` before saving/updating it for wrong/bad credentials or other possi…
-
## Why?
Currently, when the user connects a provider from the Integration store, there's no option to `Test the provider connection` before saving/updating it for wrong/bad credentials or other possi…
-
## Why?
Currently, when the user connects a provider from the Integration store, there's no option to `Test the provider connection` before saving/updating it for wrong/bad credentials or other possi…
-
## Why?
Currently, when the user connects a provider from the Integration store, there's no option to `Test the provider connection` before saving/updating it for wrong/bad credentials or other possi…
-
## Why?
Currently, when the user connects a provider from the Integration store, there's no option to `Test the provider connection` before saving/updating it for wrong/bad credentials or other possi…
-
## Why?
Currently, when the user connects a provider from the Integration store, there's no option to `Test the provider connection` before saving/updating it for wrong/bad credentials or other possi…