Texa DeskDevelopers

Actions in your systems

Ready-made connectors

Connect Paystack, Flutterwave, Monnify, M-Pesa, Shopify, WooCommerce, HubSpot, Salesforce or Zoho CRM with your keys, no code.

A ready-made connector gives Texa AI actions in a system you already use. You paste your keys, review the actions, and name them in your procedures. Set them up in Texa Desk under Texa AI → Actions → Connectors, separately for the sandbox (test keys) and live.

Connector Category Actions
Paystack payments get_payment_status · get_transfer_status (verified customers) · refund_payment (changes something; verified, with the customer's yes)
Flutterwave (v4) payments get_payment_status · get_transfer_status (verified) · refund_payment (verified, with the customer's yes)
Monnify (Moniepoint) payments get_payment_status
M-Pesa (Daraja) payments get_mpesa_payment_status: whether an M-Pesa Express request was paid
Shopify commerce get_order (verified) · cancel_order for an unshipped order (verified, with the customer's yes)
WooCommerce commerce get_order (verified)
HubSpot CRM find_customer by phone or email · open_ticket
Salesforce CRM find_customer by phone · open_case
Zoho CRM CRM find_customer by phone · add_crm_note

"Verified" means Texa AI checks who the customer is before it runs the action (a one-time code to the phone or email on record, or your own sign-in). "With the customer's yes" means it states exactly what it will do and waits for them to agree.

What you control

For each action you can change, before you save it:

  • Private outputs. An amount or a recipient's account marked private is never said back to an unverified customer.
  • Who may use it in your website or app chat: anyone, or signed-in customers only.
  • Limits on actions that move money, such as the largest refund.
  • Load at the start: a lookup that runs before Texa AI's first reply, so it already knows the customer's record.

Every call is recorded under the action (the last 50 calls), with account and card numbers, PINs, keys, emails, phone numbers and balances hidden. Test an action from the same screen: reads run against live, writes only in the sandbox.

Not listed?

Connect your own API (an OpenAPI file, or a documentation page Texa AI reads), your own server, or an MCP server. Ask for a connector at [email protected].