Skip to main content

Request an action for your product

The action packs in Settings → Support → Actions are the actions we have already built. Each one carries the assumptions of whoever asked for it first.

The Banking / Fintech pack, for example, is card and dispute operations: freeze a card, report one lost, open a dispute, change a limit. If you are a lender, none of that describes your product. Enabling it would give your customers an agent offering to freeze a card they do not have.

So there is a third option, beside "adopt a pack that nearly fits" and "get nothing": tell us what your product needs and we build it.

What a runtime action is​

Most of what Lira does is answer questions from your knowledge base. A runtime action is Lira doing something in your systems during the conversation: reading a real balance, checking a real transfer, changing something on a real account.

It works by calling your API. Lira never holds your data. When a customer asks, the agent calls the action, your system does the work and returns a result, and Lira tells the customer what happened.

Everything else in the runtime applies automatically:

  • Confirmation. Anything that changes an account asks the customer to approve it first.
  • Step-up. Sensitive actions can require the customer to re-authenticate, through your own PIN, biometric or OTP, before anything runs.
  • Policy and audit. Every call is checked against your policy and recorded.
  • Metering. Actions count against your plan.

How to ask​

  1. Go to Settings → Support → Actions.
  2. Scroll past the packs to Need an action that is not here?
  3. Choose Tell us what you need and answer three questions.

What does your product do?​

So we do not guess. "Transfers, bills payment, loans and investments" is enough. This question exists because we once described an action to a lender using a card example, having never asked.

What should Lira be able to do?​

One line, in your words. "Check the status of a loan repayment."

What should happen when it runs?​

What Lira should read or change, and whether the customer must re-authenticate first. For example:

When a customer asks about a repayment, Lira should look up their active loan and tell them the next due date and amount. Read only, no re-authentication needed.

That goes straight to the team who will build it, and we reply to you about how it would work against your API.

What happens next​

  1. We talk to you about the shape of it: which endpoint, what it returns, whether it should be gated behind re-authentication.
  2. We build it against your API.
  3. It appears in your Actions settings like any other pack.
  4. It joins the catalogue, so the next business with the same need enables it themselves without asking.

Common questions​

Can I build one myself instead?​

Yes. If you have an MCP server, connect it in Settings → Support → Actions and your own tools run under your own auth, with Lira's confirmation, step-up, policy and audit still applied. The REST adapter is the simpler path for a plain HTTP API. Requesting an action is for when neither fits, or when you would rather we did the work.

Does it cost anything?​

Building it is part of your engagement with us, and actions are metered by your plan once they run. Ask us when you send the request and we will be specific before anything is built.

Can I test it before going live?​

Yes. Actions run in sandbox against your test environment first. Nothing touches a real customer until you move the workspace to production.

What if my request is something you already have?​

Then we tell you, and you enable it in settings the same day. Asking costs you nothing.