Actions48
- Account Actions
- Blacklist Actions
- Campaign Actions
- Conversation Actions
- Custom Variable Actions
- Label Actions
- Lead Actions
- Template Actions
- Webhook Actions
Conversation → Send Message To Conversation
AI-generatedOverview
This node operation sends a message to a specified conversation within the Aimfox application. It is useful for automating communication workflows where messages need to be programmatically sent to conversations, such as customer support chats or team collaboration threads. For example, it can be used to send notifications or updates directly into a conversation based on triggers or events in an automation workflow.
Use Case Examples
- Sending a greeting message to a customer conversation when a new support ticket is created.
- Automating follow-up messages in a sales conversation to keep the lead engaged.
Properties
| Name | Meaning |
|---|---|
| Conversation URN | The unique identifier (URN) of the conversation to which the message will be sent. |
| Account ID | The LinkedIn ID of the account associated with the conversation, used to identify the correct conversation context. |
| Conversation Message | The actual text message content to be sent into the conversation. |
| Request Options | Additional settings for the request such as batching, SSL certificate validation, proxy configuration, and timeout settings. |
Output
JSON
messageId- The unique identifier of the sent message.conversationUrn- The URN of the conversation where the message was sent.status- The status of the message sending operation, e.g., success or failure.
Dependencies
- An API key credential for Aimfox API authentication
Troubleshooting
- Ensure the Conversation URN and Account ID are correctly provided and valid to avoid errors related to missing or incorrect identifiers.
- Check network connectivity and proxy settings if requests fail to reach the Aimfox API endpoint.
- If SSL certificate validation errors occur, consider enabling the 'Ignore SSL Issues' option cautiously.
- Timeout errors can be resolved by increasing the timeout setting in the request options.