Integration with TAQ Automations

Try @HumanBuy @Human SubscriptionJoin @Human Community

Introduction

TAQ (Trigger/Action/Query) Automations are designed to integrate directly and safely with @Human Agentic. They also act as a fulcrum between @Human Agentic and @Human Connections.

Integration between Agentic and TAQ Automations is two-way:

• An Agent may invoke one or more TAQ Automations ("TAQ")

• A TAQ may invoke one or more @Human Agents

Agentic Invocation of TAQ

Any Agent can be permitted to invoke a TAQ by clicking on the "Allowed TAQs" dropdown menu in the Agent configuration panel.

The permitted TAQ will then be added to the MCP (Model Context Protocol) Policy for the Agent in question.

On the TAQ side of the equation, the Trigger type should be set to "Agent Invoked" and the nature of the Agentic output to be received (usually a text string) should be defined in the parameters of the TAQ Trigger.

TAQ Invocation of Agents

An independently triggered TAQ Automation can invoke one or more Agents.

The Agent can also hand output back to the TAQ and the conversation can be continued.

Different Agents - Different Models?

You may find it useful to select different LLM models depending on the Agent's purpose. For more programmatic or simple actions, a cheaper LLM model will usually suffice.

However, for more nuanced communication (e.g. replying to customer enquiry), it makes sense to use more advanced models. In the diagram above, different Agents could employ different LLM models without impacting the design of the TAQ.