> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blnkfinance.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Define your workflow

> Plan what your Custom App should do before you write code — narrow scope, one-sentence purpose, and a clear step-by-step workflow.

<Note>
  This feature is in private beta. If you want access, please [contact Support](mailto:support@blnkfinance.com?subject=Interested%20in%20Custom%20Apps).
</Note>

Before writing code, define the workflow your app should support:

<Steps>
  <Step title="Describe your app in one sentence" id="describe-your-app">
    The best Custom Apps are focused. They help a team complete one job inside Cloud instead of trying to become a large internal system.

    <Tip>
      A good mental model is to think of each Custom App as a feature of your Blnk Cloud workspace, instead of a complete app.
    </Tip>

    **For our Stripe Sync app,** its job is:

    ```text Stripe Sync app description wrap theme={"system"}
    Import pay-ins and payouts from Stripe into Blnk and syncing them with existing customer identities in Blnk. 
    ```
  </Step>

  <Step title="Map your workflow" id="map-your-workflow">
    From there, map the work the app needs to handle. Here's the workflow for our Stripe Sync app:

    | Step             | What the app needs to do                                                                                                                                    |
    | ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
    | Sync from Stripe | Connect to a Stripe account and read pay-ins and payouts (and related Stripe ledger data as needed). Also sync the customer identities from Stripe to Blnk. |
    | Import to Blnk   | Create or update ledger transactions in the selected Cloud instance so Blnk mirrors Stripe activity.                                                        |

    This gives the app a clear boundary of what the workflow is responsible for and what should happen at each step. If done well, you can now easily switch payment providers without worrying about the Stripe data being lost.

    <Tip>
      Keep the workflow narrow. If the app starts covering unrelated jobs, you should consider splitting those jobs into separate apps.
    </Tip>
  </Step>
</Steps>

***

**Need help building your app?**

We help you build custom apps for your use case or get help building your own from scratch.