Sharing the solution here for easier access by others:
By retrieving the execution data, you can obtain the token usage from the model.
This information was originally posted in the topic here.
Since the solution provided by the original poster includes this detail (even though it's a paid option), I'm marking their reply as the solution and adding my response to the top of my question.
This approach ensures that both pieces of valuable information are easily discoverable for anyone facing a similar issue in the future.
Is it possible to run this callin.io node within the same workflow? Perhaps at the conclusion of the existing nodes.
You should place it within a sub-workflow. While it can reside in the same workflow file, I'd advise against using it in the same execution. Doing so might lead to processing a significantly larger volume of data.
Thanks for the reply. I just observed something with the data.
Is there a method to subscribe to a workflow and retrieve its results?
Another question is, what happens if I incorporate a custom node at the conclusion of the workflow?
Could you please ‘upvote’ this feature request?