Langflow
Connect a Langflow agent to Pushary so it can ask questions and send updates to your phone
Langflow agents can use Pushary through Langflow's MCP Tools component. The agent chooses when to call a tool; this connection does not enforce approval of a separate action in a flow.
Connect Pushary
You need a Pushary account with a connected phone and an API key from Pushary settings. Use the key for the account that owns your phone. Do not put it in a flow, prompt, or server URL.
- In Langflow, open Settings → Global Variables → Add New. Name the variable
PUSHARY_BEARER, choose Credential, and set its value toBearerfollowed by your Pushary API key. Save it. - Open Settings → MCP Servers → Add MCP Server and choose Streamable HTTP/SSE.
- Name the server
pusharyand set the URL tohttps://pushary.com/api/mcp/mcp. - Under Headers, set the key to
Authorizationand selectPUSHARY_BEARERas its value. Save the server. Langflow should discover the Pushary tools available to your account. - In a flow, add Chat Input, Agent, and Chat Output. Choose a model provider for the Agent. Drag
pusharyfrom the MCP sidebar onto the canvas, enable Tool Mode on the MCP Tools component, and connect its Toolset output to the Agent's Tools input.
In the Agent's instructions, tell it when to use ask_user and send_notification. For a yes/no question, use ask_user with type: "confirm" and wait for the answer. Treat no answer, a decline, or an expired question as no approval.
Check the connection
In the Playground, ask the agent to send a harmless test notification. Then ask it to send a yes/no question through ask_user, answer on your phone, and check that the answer appears in Langflow. If the notification reports no_recipients, connect a phone under Pushary Settings → Connections. If Langflow lists the tools but a call returns 401 Unauthorized, check that PUSHARY_BEARER contains the current key with the Bearer prefix. Tool discovery alone does not verify the key.
An Agent instruction is guidance, not a security gate. If approval must protect a deployment, payment, or other business action, bind the exact action and recipient in your application and verify the Pushary decision before running that action. Partner workflows that address customers use the Partner server API and customer IDs instead of this personal MCP connection.
See Langflow's MCP client guide for its current editor controls and Pushary's tool reference for the available actions.