Description
🐛 Describe the Bug
A clear and concise description of what the bug is.
When using an "extra" email conversation provider (not a default one). You must use type "Custom".
If you use type "Email" and add your conversationProviderId then it will add it to the standard/default email channel.
📍 API Endpoint
Which API endpoint does this relate to?
https://marketplace.gohighlevel.com/docs/ghl/conversations/add-an-inbound-message
✅ Expected Behavior
What should have happened?
You should reject the request when we supply:
"type": "Email"
"conversationProviderId": "exists, but actual provider type is Custom"
💻 Screenshots or Code Samples
Paste relevant markdown/code samples or screenshots.
This should be rejected since it's a type mismatch. It currently sends through the default Email provider. If we supply a customConversationProviderId set as an extra email provider you should reject this payload.
{
"conversationId": "required",
"type": "Email",
"direction": "inbound",
"subject": "test",
"conversationProviderId": "681e1b1980ee500d812e9e1e",
"emailTo": "test@test.com",
"emailFrom": "redacted"
}
This is a working request for type Custom:
{
"conversationId": "required",
"type": "Custom",
"direction": "inbound",
"subject": "test",
"conversationProviderId": "681e1b1980ee500d812e9e1e",
"emailTo": "test@test.com",
"emailFrom": "redacted"
}
🧠 Additional Context
Any other helpful information?