API for "generic" custom field
T
TI Grupo Simon
It would be very useful to have an API call
to edit a generic custom field (that could be sent to every client upon request).
I.E: If my client answers a survey for the current price of a product, an automation task
would sent a message with the content of the custom field "current.price.product".
same way we can send back to the client the content of a custom field that he/she has.
trough the API I would update this field every day.
Jerry (CEO)
Hey guys, I have been thinking about this suggestion and I believe that this is something that could be best achieved via workflows. Let me explain:
We are working on a new feature called "Shortcuts" that allows an agent to trigger a workflow manually from the messaging module (see here: https://roadmap.respond.io/feature-request/p/manually-trigger-selected-workflows-from-messaging-module-shortcuts)
If the agent were to trigger a workflows and this would have a HTTP Request Step, you could first call a third-party server to get e.g. the most current price, and then it would continue to send it via a message.
So in other words, if an Agent wanted to for example send the most current USD to EUR exchange, they would just press the Shortcut in the messaging module, the workflow would start, it would request the price from your servers, and then send it to the contact via message.
What do you think? If this will solve the issue, I will just merge this request with the Shortcut one. Thoughts?
Jerry (CEO)
Hey guys, I have been thinking about this suggestion and I believe that this is something that could be best achieved via workflows. Let me explain:
We are working on a new feature called "Shortcuts" that allows an agent to trigger a workflow manually from the messaging module (see here: https://roadmap.respond.io/feature-request/p/manually-trigger-selected-workflows-from-messaging-module-shortcuts)
If the agent were to trigger a workflows and this would have a HTTP Request Step, you could first call a third-party server to get e.g. the most current price, and then it would continue to send it via a message.
So in other words, if an Agent wanted to for example send the most current USD to EUR exchange, they would just press the Shortcut in the messaging module, the workflow would start, it would request the price from your servers, and then send it to the contact via message.
What do you think? If this will solve the issue, I will just merge this request with the Shortcut one. Thoughts?
Yan-Ru Chang
Jerry (CEO) I'm not sure if this falls in the right thread, but I'm looking for something like this:
Because messages can come from different sources X, Y, Z (or different webpages)
- We can set up various contact fields to capture this "source" details, which we will need to define when integrating it with the website
e.g.
Source: Website,
Enquiry Type: Feedback,
Page Source: https://www.google.com/feedback/
- When the messages come in, respond.io pre-fills the contact with this data (especially for new contacts)
This would make it easier for Agents to understand the user journey of the Clients, and the trigger point for the message. This would also be extremely useful for reporting, to see the breakdown of messages based on "source", where they are coming from and any other contact fields we have pre-defined.
Not sure if this has been raised before! Hope to see this soon :)
Jerry (CEO)
Hey Yan-Ru Chang, so you are looking for a way to do website attribution and get the source of the first visit stored in respond.io?
Jerry (CEO)
Hey TI Grupo Simon, can you share more information on how you would use this feature?
Custom Fields are properties of a contact, and they have a different value per contact.
Something like a "current.price.product" is a variable that doesn't necessary belongs to the contact, but to the product itself.
When using our Messages API you can always send a message with the most recent value of "current.price.product".
How do you plan using this variable? If you can share some more details it would help us to point you in the right direction (in case such a feature already exist) or better understand your requirements in case such a feature would need to be added.
Thanks!
T
TI Grupo Simon
Right!
What I need is to be able to receive client messages, query our database, send back the information to the client.
I know I can send messages and update custom fields through the API, but how do I receive/GET messages?
Respond.io receive messages from Twilio through a weebook, would it be possible to a user also have a respond.io weebok to receive messages?
I use node-RED to query our internal database and retrieve information to send back to the client
(today I send scheduled messages through Twilio API to our clients),
if I had a weebook to receive the messages that would solve my problem (with that I could do all the automation tasks via node-RED).
Going back to the "generic field", a better way to explain it is: A Snippet that could be edited through API.
That way I could keep the snippet updated with the latest info like the current price of a product and respond to the client trought a survey and automated response.
Currently I'm trying to achieve this via DialogFlow (node-RED has integration with DialogFlow) but I'm not quite there yet.
By the way nodered.org / Respond.io integration would be PERFECT!
If the integration or weebhook happens, edit snippets via API won't be necessary.
Also I'd like to say our company is really liking the platform. Support is great, quick responses and always trying to solve our needs the best way possible!
10/10 support!
Jerry (CEO)
TI Grupo Simon: This is a very interesting use-case, not something that we have considered before.
In 8.1 (in around 8-9 weeks from now) we will release webhook calls, this won't run for each message though, only for the specific triggers that we are considering for our new Workflows module:
- Conversation Opened
- Conversation Closed
- Tag Added/Removed
- Contact Field Updated
So in theory, you should be able to call a Webhook whenever an agent adds a tag (e.g. the name of the product), adding this tag will trigger a workflow that calls your webhook, and the response of the webhook (you can add the product price in the response), can then be sent to the contact.
This way you Agents will just have to add a tag, in within a second a message with the most current price will be sent to the contact.
Do you think this will help you solve your problem?
To clarify, we are expecting to release Workflows (version 8.0) in 4-5 weeks, and Webhook as workflow step in version 8.1 (around 4 weeks after).
T
TI Grupo Simon
Jerry (CEO): the new workflows sounds great! we'll wait and try it out when it launches, Thanks!