consolidate `sender_id` and `conversation_id`
See original GitHub issueCurrently we are both using sender_id
and conversation_id
in our code. This should be consolidated to conversation_id
.
Based on this forum comment https://forum.rasa.com/t/how-can-i-get-a-conversation-id-so-i-run-an-action-via-post-from-an-app/19987/5?u=tobias_wochinger
Issue Analytics
- State:
- Created 4 years ago
- Comments:13 (2 by maintainers)
Top Results From Across the Web
Messages | TalkJS Documentation
This way it's possible for you to send a batch of consecutive messages in a single request. It's also possible to combine user...
Read more >Conversation and Sender ID - Rasa Open Source
conversation ID and sender ID are the same you can have only one conversation at a time for one seder ID. If you...
Read more >Salesforce - SMS-Magic Converse Release Notes
Sender ID and Template Search in Message Composer ... in the recipient level data or used merge fields or in the messaging template...
Read more >Sequelize how to structure the chat part of the app?-postgresql
... const newMessage = await Messages.create({ senderId: req.user.id, receiverId: post.userId, message: req.body.message, conversationId:conversation.id }) ...
Read more >API Reference | Sunshine Conversations
Links the attachment getting uploaded to the conversation ID. ... Copy the serverKey and senderId from the Cloud Messaging tab in the settings...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Please, Mr. Stale Bot, don’t close this.
I think the issue is probably “stale” and minor, but it could be remain open until the documentation will unify naming, choosing a single name, maybe:
conversation_id
. In factssender
is still used:see: https://rasa.com/docs/rasa/connectors/your-own-website#request-and-response-format