Actions185
- Organization Actions
- Client Actions
- Business Context Actions
- Portfolio Item Actions
- Objective Actions
- Audience Actions
- Pain Point Actions
- Content Brief Actions
- Social Media Post Actions
- Website Content Actions
- Asset Actions
- Ephemeris Actions
- Category Actions
- Product Actions
- Customer Actions
- Order Actions
- Service Actions
- Package Actions
- Project Actions
- Ad Campaign Actions
- Ad Actions
- Keyword Actions
- Newsletter Actions
- Email Report Actions
- Opportunity Actions
- Comment Actions
- Mention Actions
- Organization Member Actions
- Client Member Actions
- Audience Pain Point Actions
- Ad Keyword Actions
- Reference Content Actions
- Reference Content Category Actions
- Lead Actions
- Lead Source Actions
- Client Module Actions
- Client Activity Actions
- Organization Activity Actions
- Marketing Strategy Actions
- Strategy Pillar Actions
- Strategic Initiative Actions
Strategic Initiative → List
AI-generatedSummary
List strategic initiatives with optional organization, client, pagination, and filter parameters.
Inputs
- organizationId — Organization to operate in. Supports 'From List' mode (search via getOrganizations) or 'By ID' mode (string ID). Default is empty (unspecified).
- clientIdSelect — Client to operate on. Supports 'From List' mode (search via getClients) or 'By ID' mode (string ID). Default is empty (unspecified).
- filters — Optional filter collection. Parameters: page (number, default 1), limit (number, default 20), status (string, default empty), search (string, default empty).
- options — Execution options collection. Parameters: simplifyOutput (boolean, default true), debugMode (boolean, default false).
Output shape
Array of strategic initiative records. When simplifyOutput is true, output is minimized to essential fields. When debugMode is true, debug information is included alongside results.
All parameters are optional. The operation respects resourceLocator modes (list via async getOrganizations/getClients or direct ID). Filter and option parameters are applied as declared in the node's UI schema.