> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/integrations/using-limio-for-salesforce/legacy-features/invoke-flows-console.md).
# Invoke Flows from Manage Subscriptions Console (Legacy)
**LFS version:** requires Limio for Salesforce v12.02 or later
Limio for Salesforce exists in two major forms: a single-page app called Manage Subscriptions (legacy), and a set of Flows representing all Limio-supported actions and journeys.
Some of the recently released features of the Limio for Salesforce package are only available at the flow level and not on the Manage Subscriptions page, so we introduce a middle layer that allows invoking flows on subscription actions within the Manage Subscriptions page.
This should be considered an intermediate step towards a full migration to Limio Flows.
All Limio Flows are managed OOTB, so start with *creating a copy of the flow you want to trigger* from the Manage Subscriptions app context. In order to map a Manage Subscriptions action to a Limio Flow Copy, navigate to the Custom Metadata Types => ic Assist Config => Subscription Actions.
Proceed with mapping an action to a copied flow by editing a JSON object in the *Config* field: add or edit an **actionToFlowMap** property in the following format **{ "action\_API\_name": "limio\_flow\_copy\_API\_name" }**.
Supported action API names are:
"remove",\
"switch",\
"renew",\
"refund",\
"change\_address",\
"change\_payment",\
"redeem\_gift",\
"pause\_print".
Flow API name can be found a flow details page.
Example:
If the config doesn't include an **actionToFlowMap** property at all, then all actions are executed as usual - in the Manage Subscriptions app context.
Actions mapped to an existing *active* Limio Flow Copy in the **actionToFlowMap** property trigger a modal window to open with a referenced flow inside. For the actions that are *not* mentioned in the **actionToFlowMap**, the behaviour remains unchanged.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.limio.com/integrations/using-limio-for-salesforce/legacy-features/invoke-flows-console.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.