An action is something Texa AI may do in your systems: look up a transfer, check an order’s delivery, block a card or start a refund. Texa AI proposes it, your approved procedures allow it, and the customer says yes before anything changes.
1. Connect a system
Go to Texa AI → Actions → Connectors. Keys are stored encrypted and never shown again.
A ready-made connector
Switch on Paystack, Flutterwave, Monnify, M-Pesa, Shopify, WooCommerce, HubSpot, Salesforce or Zoho CRM, and enter its keys.
Your own system
Under Your own system, Texa can call your API, or send each request to your server:
- Texa calls your API. Enter the API address and how it signs in: a bearer token, an API key in a header, a username and password, OAuth 2.0 (client credentials), or signed requests (HMAC).
- Your server runs it. Texa sends each request to your server, signed, or over a connection your server opens. Your code answers with the results.
- An MCP server. Enter the MCP server address, then Import tools.
Sandbox and live keys are kept apart. With sandbox keys nothing real moves. With live keys, real customers and real money are involved.
Import from an OpenAPI document
Upload your OpenAPI 3 document. Every operation becomes a draft action for you to review. Pick the ones Texa AI should use, and choose Save the picked actions. Actions that change something are marked Changes something.
2. Review each action
Go to Texa AI → Actions, open an action, and check:
- Name (how procedures refer to it) and What it does (Texa AI reads this to know when it fits).
- Who can use it: Verified customers only for anything private.
- Its inputs, such as a transfer reference. Give a text input a format, such as
AP-12345, so Texa AI asks again for a wrong one. - Its outputs, and which are Never said back to the customer before verification.
- For money: the most it may move at once, in naira. Texa AI refuses any amount above this.
- Time limit (ms): on a call, Texa AI says a holding line while it waits.
- Run this lookup before Texa AI’s first reply: with the customer’s phone and email, so it starts each conversation knowing their record.
Texa AI may only use an action in a step of an approved procedure, and never on a customer’s word alone.
3. Test it
Choose Test on an action and enter test inputs. In live, only lookups run from Test, and changes are tested in the sandbox. You’ll see What Texa AI would receive.
See every call
Each action keeps its last 50 calls: what Texa AI sent and what came back. Account and card numbers, PINs, keys, emails, phone numbers and balances are hidden.
Verifying a customer with a code
If your system has no one-time code of its own, choose Use Texa-sent codes. Texa texts a 6-digit code to the number your system has for the customer.
Behind your firewall
Banks whose core systems can’t be reached from the internet use Texa Relay.

