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…

मूल्य

मुफ़्त Action

एकीकृत भुगतान

अभी समर्थित नहीं

• titlestring

  आवश्यक
  The title for the new root folder created from the blueprint.
• parentstring

  आवश्यक
  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

  आवश्यक
  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.

• data

  आवश्यक
  Data from the action execution
• errorstring
  Error if any occurred during the execution of the action
• successfulboolean

  आवश्यक
  Whether or not the action execution was successful or not

अभी कोई सत्यापित संबंधित उपयोग मामला लिंक नहीं है।