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

# Custom Workflows

> Choose the data you need, how users share it, and when your application can proceed.

Use this guide when your application needs a different combination of products or data than the other vertical guides describe. Decide what information you need and how users will share it, then choose the guides and endpoints for your implementation.

## Choose the implementation path

<CardGroup cols={2}>
  <Card title="Verifications" icon="badge-check" href="/verifications/overview">
    Order a report, track its status, and retrieve the completed result.
  </Card>

  <Card title="Data APIs" icon="database" href="/data-apis/overview">
    Retrieve records to use in your own calculations or review process.
  </Card>
</CardGroup>

## Define the workflow

Before implementing, identify:

| Decision          | Questions to answer                                                                                                 |
| ----------------- | ------------------------------------------------------------------------------------------------------------------- |
| Entry point       | Will users connect inside your application, through an email/SMS invite, or through direct login to a known source? |
| Account scope     | Can one account satisfy the request, or must the user connect every relevant income source?                         |
| Data scope        | Which [data sets](/overview/data-structure/data-sets), report types, and history windows are required?              |
| Readiness         | Can processing begin from one resource event or partial history, or must the workflow wait for all initial data?    |
| Fallback          | What happens when a source cannot be found, authentication fails, or the required data does not arrive?             |
| Return experience | Does the workflow need reconnection, updated data, additional documents, or another report later?                   |

## Implementation checklist

1. Create one Argyle [user](/api-reference/users) and retain the ID for the entire workflow.
2. Choose a [Link account-connection experience](/workflows/account-connections), a hosted invitation, or a verification session.
3. Store every returned [account](/api-reference/accounts) ID and track account status independently.
4. Subscribe to the account, resource, and synchronization webhooks that prove your required data is ready.
5. Retrieve records through the relevant list endpoints, follow pagination, and retain resource IDs for later updates.
6. Add an application-level timeout and a clear path for connection errors or incomplete data.
7. Handle [Document Uploads](/workflows/document-processing), [reconnections](/workflows/reconnecting-accounts), and [ongoing refresh](/overview/ongoing-refresh) when the workflow requires them.
8. Delete users or accounts when your application no longer needs them, according to your retention requirements.

Test success, multiple-account, incomplete-data, reconnection, and fallback scenarios in [Sandbox](/overview/sandbox-testing). Use [Data Delivery and Readiness](/overview/data-delivery) to select the correct synchronization events and the [API Reference overview](/api-reference/overview) to select the endpoint family.