Skip to main content
The Select Accounts node lets you define which Snapchat 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 Snapchat Ads steps by centralizing account selection.

​
When to Use It

Use this node when:
  • You want to avoid selecting the same Snapchat 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
  • Managing multiple client accounts or business units
  • Creating scalable reporting workflows

​
Inputs

FieldTypeRequiredDescription
Selection ModeSelect dropdownYesChoose how to define your accounts: manual, all, or filtered
AccountsMulti-selectYes (manual)Manually select Snapchat Ads accounts to use in later nodes
FiltersText filterYes (if filter mode)Filter accounts by name or ID using text conditions
LimitNumberNoMax number of accounts to return in filter or all mode

​
Selection Modes

​
Manual Selection

Pick specific accounts one by one from a dropdown list. Best for:
  • Small, known account sets
  • Specific campaign analysis
  • One-off reports

​
Select All Available

Automatically includes all Snapchat Ads accounts tied to the authenticated connection. Best for:
  • Agency reporting across all clients
  • Comprehensive performance analysis
  • When account structure changes frequently

​
Filter by Name/ID

Define rules (e.g., “Name contains ‘brand’”) to select accounts dynamically. Best for:
  • Large account portfolios
  • Accounts following naming conventions
  • Automated workflows that adapt to new accounts
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 Snapchat 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
  • Account Type: Business account classification
  • Permissions: Available operations for each account
  • Currency: Account currency settings
Example Output: 
{
  "data": [
    {
      "id": "12345678-1234-1234-1234-123456789012",
      "name": "Brand Campaign Account",
      "status": "ACTIVE",
      "type": "BUSINESS",
      "currency": "USD",
      "permissions": ["READ", "WRITE"]
    }
  ]
}

​
Credit Cost

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

​
Example Use Cases

​
Scenario 1: Daily Multi-Account Reporting

[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: 
Insert Dynamic Data → Select Accounts → Accounts

​
Scenario 2: Client-Specific Reporting

Use filters to automatically select accounts for specific clients: 
Filter: "Name contains 'ClientA'"
This will automatically include all accounts with “ClientA” in the name, making it easy to scale as you add new accounts for that client.

​
Scenario 3: Performance-Based Account Selection

Combine with conditional logic to select accounts based on performance criteria or account characteristics.

​
Configuration Tips

​
Effective Filtering

Name-based Filtering:
  • Use consistent naming conventions across accounts
  • Filter by client name, campaign type, or business unit
  • Examples: “Contains ‘Q4’”, “Contains ‘Retail’”, “Contains ‘TestAccount’”
ID-based Filtering:
  • Useful when you have specific account IDs to include/exclude
  • More precise than name-based filtering
  • Examples: “Contains ‘1234’”, “StartsWith ‘snap’”
Combination Strategies:
  • Use multiple Select Accounts nodes for complex logic
  • Combine “all” mode with downstream filtering in report nodes
  • Create reusable account groups for different purposes

​
Workflow Optimization

Single Source of Truth:
  • Use one Select Accounts node per logical account grouping
  • Reference the same selection across multiple downstream nodes
  • Update account selection in one place when needed
Scalability:
  • Design filters that automatically include new accounts
  • Use naming conventions that support automated selection
  • Test filters with edge cases and account changes
Performance:
  • Limit large account selections when appropriate
  • Consider the downstream impact of account count on report performance
  • Use caching for frequently accessed account lists

​
FAQs

Use Select Accounts when:
  • Multiple report nodes: You have several Snapchat Ads nodes in your workflow
  • Complex filtering: You need dynamic account selection based on naming or criteria
  • Reusability: You want to reuse the same account set across different workflows
  • Automation: Building AI agents or automated workflows that need to discover accounts
  • Large account sets: Managing many accounts where manual selection is impractical
Use direct selection in Get Report when:
  • Single report: You only have one Snapchat Ads report node
  • Simple selection: You know exactly which accounts you want
  • One-off analysis: Ad-hoc reporting that won’t be repeated
  • Small account count: Only a few accounts to select
Pro tip: Select Accounts is particularly valuable for agencies managing multiple client accounts or businesses with complex account structures.
Best Practices for Account Filtering:Naming Convention Strategy:
  • Client-based: “ClientName_CampaignType_Region”
  • Business unit: “BU_Finance_2024”, “BU_Marketing_Q4”
  • Campaign type: “Brand_Awareness”, “Performance_Sales”
  • Testing: “Test_”, “Draft_”, “Staging_”
Filter Examples:
Name contains "2024" - Current year campaigns
Name contains "Brand" - Brand awareness accounts
Name contains "Performance" - Performance marketing accounts
Name not contains "Test" - Exclude testing accounts
Advanced Filtering:
  • Regex patterns: For complex naming structures
  • Multiple criteria: Combine inclusion and exclusion rules
  • ID patterns: Use account ID patterns when available
Maintenance Tips:
  • Document your naming conventions
  • Test filters when adding new accounts
  • Regular audits to ensure filters capture intended accounts
  • Consider account lifecycle and naming changes
Yes! Multiple Select Accounts nodes enable sophisticated account management:Common Patterns:Different Account Types:
[Select Accounts: Brand Campaigns] → [Brand Performance Report]
[Select Accounts: Performance Campaigns] → [Performance Report]
[Combine Reports] → [Unified Analysis]
Geographic Segmentation:
[Select Accounts: US Accounts] → [US Report]
[Select Accounts: EMEA Accounts] → [EMEA Report]
[Select Accounts: APAC Accounts] → [APAC Report]
Client Separation:
[Select Accounts: Client A] → [Client A Dashboard]
[Select Accounts: Client B] → [Client B Dashboard]
Benefits:
  • Parallel processing: Run reports simultaneously for different account groups
  • Organized workflows: Clear separation of account types and purposes
  • Flexible analysis: Different metrics or date ranges for different account types
  • Scalable architecture: Easy to add new account groups or clients
Considerations:
  • Each Select Accounts node runs independently
  • No credit cost for multiple selections
  • Outputs can be combined downstream if needed
Scenarios and Solutions:Empty Results Causes:
  • Restrictive filters: Filters that don’t match any account names
  • Typos in filters: Misspelled account names or criteria
  • Account changes: Accounts renamed or removed since filter creation
  • Permission issues: Accounts you no longer have access to
Handling Empty Results:
  • Workflow stops: Downstream nodes won’t execute without account data
  • Error prevention: Test your filters with known account names first
  • Fallback strategies: Use broader filters or “all” mode as backup
Best Practices:
  • Test filters regularly: Especially in automated workflows
  • Monitor account changes: Set up alerts for account additions/removals
  • Flexible filtering: Use partial matches rather than exact matches
  • Documentation: Keep track of account naming patterns and changes
Troubleshooting Steps:
  1. Check account access: Verify you can see accounts in the Snapchat Ads interface
  2. Test with “all” mode: See all available accounts first
  3. Simplify filters: Start broad and narrow down gradually
  4. Verify spelling: Check filter text against actual account names
  5. Check permissions: Ensure you have read access to target accounts
Business Manager Considerations:Connection Setup:
  • Each Snapchat Ads connection is tied to specific business manager access
  • You may need multiple connections for different business managers
  • Account access depends on your permissions in each business manager
Multi-Business Manager Strategy:
  • Separate workflows: Create different workflows for each business manager
  • Multiple connections: Use different Snapchat Ads connections for each business manager
  • Consolidated reporting: Combine data from multiple business managers downstream
Account Organization:
  • Clear naming: Include business manager or client identifiers in account names
  • Consistent structure: Use similar naming patterns across business managers
  • Access documentation: Maintain records of which accounts belong to which business managers
Workflow Design:
[Connection A: Business Manager 1] → [Select Accounts A] → [Report A]
[Connection B: Business Manager 2] → [Select Accounts B] → [Report B]
[Combine Data] → [Unified Analysis]
Best Practices:
  • Regular access audits: Verify account access across business managers
  • Consistent processes: Use similar account selection patterns across business managers
  • Error handling: Plan for account access changes or business manager modifications
  • Documentation: Maintain clear mapping of accounts to business managers
⌘I