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

# Select Accounts

> Select Microsoft Ads accounts to use in other nodes

The **Select Accounts** node lets you define which Microsoft Ads accounts to use in downstream nodes. You can select them manually, fetch all available, or use filters. This is an **AI-powered node** that can understand natural language instructions.

This node simplifies workflows with multiple Microsoft Ads steps by centralizing account selection.

***

## When to Use It

Use this node when:

* You want to avoid selecting the same Microsoft Ads accounts in every report node
* You're building larger workflows and want to manage account selection dynamically
* You need to reuse a filtered group of accounts based on naming or ID
* Building an AI agent that needs to list accounts before running reports

***

## Inputs

| Field              | Type            | Required             | Description                                                    |
| ------------------ | --------------- | -------------------- | -------------------------------------------------------------- |
| **Selection Mode** | Select dropdown | Yes                  | Choose how to define your accounts: manual, all, or filtered   |
| **Accounts**       | Multi-select    | Yes (manual)         | Manually select Microsoft Ads accounts to use in later nodes   |
| **Filters**        | Text filter     | Yes (if filter mode) | Filter accounts by name or ID using text conditions            |
| **Limit**          | Number          | No                   | Max number of accounts to return in **filter** or **all** mode |

***

## Selection Modes

* **Manual Selection**: Pick specific accounts one by one
* **Select All Available**: Automatically includes all Microsoft Ads accounts tied to the authenticated connection
* **Filter by Name/ID**: Define rules (e.g., "Name contains 'brand'") to select accounts dynamically

The **Accounts**, **Filters**, and **Limit** fields will appear or hide automatically based on your selection mode.

***

## Output

The node returns the selected **account IDs** and **account information** under a `data` key. You can reference this in any downstream Microsoft Ads node.

**Account Selection Output:**

* **Account IDs**: Unique identifiers for selected accounts
* **Account Names**: Human-readable names for each account
* **Account Status**: Active/inactive status information
* **Permissions**: Available operations for each account

***

## Credit Cost

* **Cost per run**: Free to use (0 credits)

***

## Example Use Case

Let's say you run daily reports for multiple Microsoft Ads accounts:

```plaintext theme={"dark"}
[Recurring Schedule] → [Select Accounts] → [Get Report A]
                                        → [Get Report B]
                                        → [Analyze Data]
```

Now you only have to define the account list once. Each report node can reference it via:

```plaintext theme={"dark"}
Insert Dynamic Data → Select Accounts → Accounts
```

***

## Configuration Tips

* **Authentication**: Ensure your Microsoft Ads connection is properly configured and has necessary permissions
* **Account Access**: Verify you have access to all accounts you want to select
* **Naming Conventions**: Use consistent account naming for easier filtering
* **Error Handling**: Configure retry policies for reliable automation
* **Testing**: Use test mode to validate your configuration before going live

***

## FAQs

<Accordion title="Can I reuse this account selection across multiple report nodes?">
  Yes. That's exactly the point. Once you configure this node, other Microsoft Ads nodes like **Get Report** can use its output via dynamic inputs.
</Accordion>

<Accordion title="How do I reference this in another node?">
  In any downstream Microsoft Ads node, click the dynamic data button (+) next to the **Accounts** input, then choose: **Select Accounts → Accounts**
</Accordion>

<Accordion title="Why are some fields hidden or disabled?">
  Fields like **Accounts**, **Filters**, and **Limit** are shown conditionally based on your **Selection Mode**. Changing modes resets incompatible fields to avoid conflicts.
</Accordion>

<Accordion title="How many accounts can I select?">
  * In **manual** mode: no strict limit, but performance may decrease with many accounts
  * In **all** or **filter** mode: up to the API limit (with an optional `limit` parameter)
</Accordion>

<Accordion title="Can I filter by both Account Name and ID?">
  Yes. In filter mode, use one or more conditions like:

  * Name **contains** "store"
  * ID **equals** "1234567890"
</Accordion>

<Accordion title="What if I don't want a limit on the number of accounts?">
  Just leave the **Limit** field blank. All matching accounts will be selected (up to the internal API limit).
</Accordion>

<Accordion title="Why am I getting 'No accounts found' errors?">
  This can happen when:

  * Your filters are too restrictive
  * You don't have access to any Microsoft Ads accounts
  * Your connection needs to be refreshed
  * The accounts are suspended or inactive
  * You lack proper permissions for the specific accounts
</Accordion>

<Accordion title="Why can't I see certain accounts?">
  Account visibility depends on:

  * **Permissions**: You need at least read access to the account
  * **Account status**: Suspended accounts may not appear
  * **Connection scope**: Ensure your Microsoft Ads connection has proper scope
  * **Management hierarchy**: You may only see accounts you directly manage
  * **Azure Admin access**: Some accounts may require global Azure Admin permissions
</Accordion>

<Accordion title="I have connection issues - what should I do?">
  If you're experiencing connection problems:

  * Verify your Microsoft Ads account has proper permissions
  * Consider creating a new Microsoft Advertising account specifically for your global Azure Admin
  * Ensure the account has necessary permissions to access the data you need
  * Try refreshing your connection credentials
</Accordion>