Telnyx的动态

Transcript

All right. Week 9 of Workflow Wednesdays. Thanks again for watching and joining with me. Today I wanna go through a particular feature that some people may not be aware of, but definitely a future that will help your workflow scale as they become more complex as you add more nodes. And I'll go through a particular example that I have today, a workflow, very simple workflow, which just to show you the power of this particular feature called the global data prefix and how it can help you. Keep it cleaner workflow and make it more easy to understand, especially the parts that actually require understanding the dependencies of data between those nodes. So if you have ever checked out our documentation section, we have an article that goes through this example there as well in further detail for your own review. So go to my workspaces and let's begin. So I have a. Uh, workspace setup already called global prefix demo on. Inside it I have my global prefix workflow. So this is this is what it looks like before we make any changes. So let's describe what we see here first. So the IMM call node is the first node, the trigger node in our workflow. If I receive a call to the number associated with this inbound call trigger, it will process the next set of nodes and pass the data on. So on a passes the data onwards through the data anchor here. And in this case, the data anchor is automatically connected to the answer note. So anytime you connect a node in your workflow, drag from the web hook anchor over to another node, let's say. Let's look for a. Call node like hang up, you're automatically passing in some key information that's required to run the workflow, in this case the call control ID. In order to execute commands or these nodes through our Voice API, you need to always ensure that the call control ID, which is the unique identifier of this call, is included in each of these nodes so that we know which call to issue that command on. And whenever you drag across from one of the web anchors like we just did there called that speak ended on the speak text node, you'll automatically pass through that data. You don't drag over and you just right click anywhere and then connect the. No node answer Node let's say to bridge and then the data manually. You have to uh. Pass in. Their cult control ID here as well. So just bear that, bear that in mind. It's important to consider when you're building out your posts, but we want to avoid passing through data lines that are unnecessary data from nodes like the answer. There's nothing that the answer provides as output that's kind of relevant to the next nodes. So it's. Note. We look back at our entire workflow again. And. The call, the inbound call will pass through this call dot initiated web hook that is now the information from this web hook is now accessible and the answer node and that's how I can get access to the control ID by doing the open curly braces specifying the values that I want. But that's kind of the only thing that's interesting in here. You know, I just want to answer the call it's kind of. Not really important. Anything else outside of that information that I want to do next? What you can see that the answer node is passing data to the switch to the HTTP client to the date time value as well. Let's include that there for the sake of the demo purpose and onwards straight through to the gather. The whole point of the global prefix is to allow that node and that node data to become accessible throughout the entire work. And what you get then is not having to pass in, let's say the information from this node all the way up to the handle, and you get. Workflows that start to come a little bit more difficult to view, right, because you've got more lines involved. We really only care about the execution, the flow of execution, which are the black edges here. The black lines and the data lines should only really apply between the nodes that will actually share data between. So if I think about it here, the date time node is useful because maybe I want to pass through the daytime into the current datetime into this next node, right? Gather using AI node. And we do that here by connecting the output of the daytime node as the input into the galleries and AI node. And we access it through the dynamic variable syntax as seen here because that's what is available to us utility that daytime, that daytime, right? This is the information that you'll see here. 20250306. Offset UTC. Let's see what happens when we add the global prefix. So I'm going to click my inbound call mode, go to the node settings on the top right hand side here I'm going to enable the prefix. I'm going to give it name. I'm going to call it in the on call info. I'm going to add that prefix. And if you see over at our inbound call, the data anchor is going to disappear. Data anchors gone now, no more blue line connecting from the inbound call node to the answer node. An importantly again, this prefix is now added. So anytime we want to access the information from this node, we use the dynamic variable syntax. We include this prefix at the beginning and then we'll be able to access all the other properties inside that. Very important thing to note though is that when you do enable the prefix, make sure to update the downstream nodes, the next nodes that are connected. In this case, here we have the call control ID. This is no longer applicable because the data line is not passed or connected to the answer. So I need to update this open curly bracket and pass through the inbound cosmical call. Initiate the call control ID instead. Lucent tax means that the dynamic dynamic variable is valid and it is accessible. We can access it from this now there. And likewise, now I wanna get rid of the data lines that are outputted from the answer node, because they're just not applicable. There's nothing in the answer now that's really important that other downstream nodes further need to be aware of. So I'm going to get rid of it all. Just bear in mind that while I have enabled that global prefix on the inbound call, since this answer notice still passing through its data to the gather using AI node, technically speaking this is still valid. Because it's accessing the web hook information from this answer node, for which we can still access the call control ID property. But we don't want to do that. We want to remove the need for passing through the control ID across nodes when we've just pretty much made it accessible globally. So I'm going to get rid of this anchor here as well. And I'm going to have to update the gather using AI control ID field to use. The inbound called info global prefix instead. So now when we look at our graph right? Now now that the daytime node is part, an important note for me that outputs data into the gather using Arnoldt speak. Note because these two nodes need to use the values that this data outputs. Whereas with the answer at all, there was nothing really important in that mode. So that's the idea behind the global prefixes. Umm, this is a very simple workflow for now that talks about why it's beneficial. And you can see that here straight away that we don't have as many blue lines as we did initially throughout the workflow. While it might not look too bad here right now, uh, it's when you have workflows that probably increase the size. To 20 plus notes and where you definitely don't want to have blue lines attached everywhere that the global prefix node, um, or rather the global prefix setting on your inbound call or any other note. It's not just limited to the, the trigger note that we have in our example here becomes accessible. Just say that you know, name them accordingly so that you can understand importantly at which point they should apply. Maybe I won't want to, uh, give. The HTTP client node, a global prefix because maybe some future now down the line that maybe you haven't connected up yet, we'll be able to access that based on the prefix that ISIL. And that avoids me able to drag you're really, really long line all the way over to whatever node it is in the workflow. And again, it makes the workflow look a lot cleaner. So that's everything today on the global data prefix. Check out the documentation there again for more. Specific details around this example, but I do hope it helps you in making sure that your workflows, especially those that grow in size, come a lot cleaner in its usage. So thank you.