Aident logoAident logo centerAident Loadout
PricingDocs
ENStart Now
AppsWrike ToolsWrike Launch Folder Blueprint Async
Wrike Tools

Wrike Launch Folder Blueprint Async

Asynchronously launches a new project or folder structure in Wrike from a specified Folder Blueprint. Important Notes: - The folder_blueprint_id must be an actual launchable blueprint, NOT a BpRoot container. - Use WRIKE_LIST_FOLDER_BLUEPRINTS to get blueprint IDs. Look for chil…

Write actionRisk level 2 of 5OAuth connection
Use Wrike Launch Folder Blueprint Async

Pricing and limits

Aident logo

Product

Aident LoadoutOpen-CUAK

About

AppsSkillsUse CasesDocsBlogPricingDownloadsPrivacy PolicyTerms of Service

Alternatives

vs Composiovs Zapier
llms.txtGet an AI summary of Aident LoadoutSummarize with ChatGPTSummarize with ClaudeSummarize with GeminiSummarize with Perplexity

© Aident Labs, 2024-2026

Pricing
Free
Unified payment
Not currently supported

Inputs

  • titlestring
    Required
    The title for the new root folder created from the blueprint.
  • parentstring
    Required
    The unique identifier of the parent folder where the blueprint structure will be created. Use WRIKE_GET_FOLDERS to get valid folder IDs.
  • entry_limitinteger
    The maximum number of tasks and folders that can be created from the blueprint. This limit must be between 1 and 250, inclusive. If the blueprint contains more items, the operation may fail or be partially completed.
  • title_prefixstring
    A prefix to be added to the titles of all tasks and folders copied from the blueprint. If not provided, original titles are used.
  • reschedule_datestring
    The new start date for all rescheduled tasks in the format YYYY-MM-DD. If provided, tasks will be rescheduled based on this date and the reschedule_mode.
  • reschedule_modestring
    Defines how tasks are rescheduled. Common modes might include shifting tasks relative to the reschedule_date or anchoring them. Consult Wrike API documentation for specific values. Examples: 'Preserve', 'Shift'.
  • copy_attachmentsboolean
    If true, attachments from the blueprint will be copied. Defaults to true if not specified.
  • copy_descriptionsboolean
    Specifies whether to copy descriptions from the blueprint's tasks and folders. If true, descriptions are copied; otherwise, they are left empty. Defaults to true if not specified.
  • copy_responsiblesboolean
    If true, responsible assignments from the blueprint will be copied to the new tasks. Defaults to true if not specified.
  • copy_custom_fieldsboolean
    If true, custom field values from the blueprint will be copied to the new tasks and folders. Defaults to true if not specified.
  • folder_blueprint_idstring
    Required
    The unique identifier of the folder blueprint to be launched. Must be an actual blueprint ID (not a BpRoot container). Use WRIKE_LIST_FOLDER_BLUEPRINTS to get valid blueprint IDs - look for blueprints that are NOT 'BpRoot' scope.
  • notify_responsiblesboolean
    If true, users assigned as responsibles for tasks in the blueprint will be notified. Defaults to true if not specified.

Observable output

  • data
    Required
    Data from the action execution
  • errorstring
    Error if any occurred during the execution of the action
  • successfulboolean
    Required
    Whether or not the action execution was successful or not

Skills that use this Action

Related use cases

No verified related use cases are linked yet.

Official source

Provider source

Skills that use this Action

No published Skills explicitly reference this Action yet.