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
Output
The node returns the selected account IDs and account information under adata
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: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
Can I reuse this account selection across multiple report nodes?
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.
How do I reference this in another node?
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
Why are some fields hidden or disabled?
Why are some fields hidden or disabled?
How many accounts can I select?
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)
Can I filter by both Account Name and ID?
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”
What if I don't want a limit on the number of accounts?
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).
Why am I getting 'No accounts found' errors?
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
Why can't I see certain accounts?
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
I have connection issues - what should I do?
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