Using Metadata/Variables in 1.5 for Outbound Calls Issues | Thoughtly Community

Using Metadata/Variables in 1.5 for Outbound Calls Issues

Is there anyone using 1.5 and outbound calls using metadata/variables? I am using {Description} for example, which I passed into the API variables. 1.0 has no issue replacing {Description} with the variable passed, but now 1.5 actually says "Description"

19 comments

Tony K
·
·
Torrey Leonard after the call, I decided to give 1.5 another shot. Do you know if you guys are accepting metadata through the API just like 1.0 is accepting the metadata?
Torrey Leonard
·
·
Nice! Yes, we should be. Let me check with the team
Chris Guzman
·
·
good question here
Tony K
·
·
works perfectly for me in 1.0, but not in 1.5
Chris Guzman
·
·
what meta data do you pull to have the agent say the first name (when it pulls the data from a form builder)?
Tony K
·
·
I am sending in metadata with a name, so I reference that
Tony K
·
·
ie - if you pass in "firstName" then in the node I use {firstName}
Tony K
·
·
Torrey Leonard were you able to confirm
Alex Casella (Thoughtly)
·
·
should be working in v1.5
Chris Guzman
·
·
What worked for me was {Contact: Name} in zapier and now it says first name
Tony K
·
·
So Zapier is sending the string Contact: Name = "John" ???
Tony K
·
·
I would assume it would send something like "Name": "John" and then in thoughtly you would use {Name}
Alex Casella (Thoughtly)
·
·
David Osemwegie can you help here?
Tony K
·
·
I was asking Chris, as I am passing to 1.0 and it works perfectly from API
👍1
Tony K
·
·
I just changed the id for the 1.5 agent I added and it wasn't working
Tony K
·
·
so that is why I am wondering if it is handled differently
Tony K
·
·
are you able to help me with verification?
Tony K
·
·
I have my incorporation documents
Chris Guzman
·
·
Call isnt triggering from zapier. it was working earlier.. any reason to why that is?