Import / export complete playbook

Ability to prepare use case on non-production environment and export them to production environment.
A Playbook may include Rules, Workflow, Fields, Artifacts, Data Tables, Blocks, Scripts, Widgets, Dashboard, Messages, Notification, Wiki Pages, Incident Tabs, Groups, Messages Destinations, Phases, Tasks, Incident Types, Workspaces, Roles, Functions...

  • Guest
  • Apr 23 2018
  • Future consideration
  • Admin
    MARTIN FEENEY commented
    8 May, 2020 10:33am

    The mechanism to identify a set of components that make up a playbook, would be the same mechanism you could use to identify a smaller subset of components, even individual ones. We would not propose having one mechanism for individual component export and a different one for exporting multiple components.

  • Guest commented
    8 May, 2020 09:13am

    I don't understand why the idea I uploaded merged into this? Doesn't this mean complete export function of whole components up there? What I wrote was a component of those components to be able to be exported. (ex. a single workflow from Workflows to be exported)

  • Admin
    MICHAEL LYONS commented
    1 May, 2020 02:52pm

    We currently have designs under way and hope to get them scheduled in the roadmap soon. Our Apps and App Host deliverable built out much of infrastructure needed to solve this problem so we will continue to build on top of that to deliver selective exporting this year.

  • Guest commented
    29 Apr, 2020 11:45am

    What is the status of this idea? The last admin post is nearly a year old. And this is the far most expected functionality.

  • Guest commented
    13 Dec, 2019 09:27am

    Incredibly useful functionality

  • Guest commented
    20 Nov, 2019 10:02am

    Agree with the overall idea, want to extend it as following:

    - Export files from Resilient

    - Have it edited from scripts / manually

    - Import to have changes implemented


    Could be very useful for overall name changes, broader changes of core things (e.g. several field names has changed, so do a search & replace on the export instead of the slow and tedious web GUI).

  • Guest commented
    27 May, 2019 07:48pm

    This i needed. If I want to devleop my worklows as CODE and strore in version control I cant at this point.

  • Admin
    MARTIN FEENEY commented
    20 May, 2019 09:16am

    Hi folks,

    We wanted to give a general update on this Idea which is far and away our most popular one based on votes.

    How we handle playbooks is of strategic importance to our product roadmap.

    Our current priority in this respect is;
    - Playbook UI Refresh where we look to improve the UX of working with the various components of a playbook.
    - Extensions, where we look to improve the UX of installing apps and their associated configs (which are themselves components of a playbook)
    - Tagging all components of a playbook
    - Export/Import leveraging tagging.

    The UI refresh and extensions are currently in progress and we hope to move to the other items including this Idea as per the above priority.

    We hope you appreciate there are logical dependencies between the above items that are driving this sequence and thank you for your patience while we work on this area.

    Please feel free to contact any of the product management team for more details or clarification on our plans in this respect.

    On behalf of the Resilient PM team,


  • Guest commented
    16 May, 2019 01:50pm

    Could be used in export TAG related objetcs in order to allow export of all objects using the same TAG

  • Guest commented
    4 Apr, 2019 04:31pm

    Feature really useful for compliance needs, in order to give evidenceof processes and playbooks with auditors

  • Guest commented
    19 Feb, 2019 02:33pm
    Workaround : this has slipped out into the wild now - which is great news for our customers with prod and pre-prod environments. See the function developer guide section 5.7 
    If you wish to share Resilient components, such as rules, scripts, workflows and custom fields, without deploying a function, you can package those components in a .res file using the resilient-circuits extract command then import the file into a Resilient platform.
    For example, you created a script, playbook, or workflow then determined that these components would be useful on another Resilient platform.
    To create a res file containing these components, perform the following:
    1. Make sure that you have the Resilient export file that contains the components you wish to package.
    2. Enter the following command to package the components and zip the resulting output file: resilient-circuits extract –-script --workflow --rule -o .res --zip
    3. Copy the file to the host system of the Resilient platform.
    4. Log in to the Resilient platform and use the import feature to import this file. You can find the import feature by clicking Administrator Settings and selecting the Organization tab.
    Refer to the Resilient Incident Response Platform System Administrator Guide for details.
  • Guest commented
    14 Jan, 2019 10:35pm

    We have compliance requirements to share our processes and playbooks with our auditors.  Not having this feature has kept us from using "Tasks" within Resilient.  Right now each incident that's created gets task with a link to a Word document playbook on our SharePoint site for the applicable incident category .  Talk about not using the product to its potential...

  • Guest commented
    13 Dec, 2018 03:07pm

    For this feature I'd like to also emphasize the importing and exporting of Wiki Pages from Organizations, or just the ability to do so in general. While Organizations can be separate, similar functions can exist across these silo'd instances. The ability to export into a .res or .xml/.csv, etc., would be helpful.

  • Admin
    Brenden Glynn commented
    9 Aug, 2018 10:57pm

    Related Idea:

  • Guest commented
    25 May, 2018 08:11am

     I vote for this enhancement

  • Guest commented
    23 Apr, 2018 08:37pm

    Feature really missing