Skip to content

Help shape the future of Box

Welcome to Box Pulse, our product feedback tool powered by UserVoice. Got an idea for how to improve Box? Share it with us and gather support or vote on other people's ideas. Your feedback is essential to informing roadmap decisions and shaping the future of our products. Thanks for joining our community!

See user guide here.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

29 results found

  1. Enable processing in folders with editor permissions in Box Automate

    Currently, due to Box restrictions, if the option “Limit sending invitations to collaborators to folder owners and co-owners only” is enabled for a folder specified in an Automate flow, and the flow owner specifies a folder to which they have been invited as an editor, errors will occur for “task assignments, file operations, and folder operations,” causing the process to fail.

    Many companies allow co-owners and higher-level users to be invited, but if that were the case, it would significantly reduce usability under the current system. Therefore, I would like the workflow to function properly even when folders with editor…

    41 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Task Feature in Box Automate

    In the current Box Automate, the Task outcome fails when the folder or enterprise setting is "Only folder owners and co-owners can send collaborator invites", which we understand is officially stated on the Box Support page.
    However, many companies in Japan use this configuration, making the Task feature in Box Automate practically unavailable.

    Our understanding was that Box had initially stated the existing Box Relay features would remain available after the upgrade to Box Automate. If that is not the case, this may impact customers’ existing business operations, which we consider to be a concern.

    We would like to request…

    29 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. External Notification Support

    Allow for notifications to be sent to external (non-box users) partners, vendors, submitters, etc as part of an automate workflow.

    Box Forms and File Request allow for seamless ingestion of content and metadata but does not allow for an easy way to update those submitters after their document has been ingested. Many times there is a formal internal review process where a submitter would want to receive an email notification as the document or application moves through the review process inside of Box.

    Example use cases: notifying an external submitter that their submission has been rejected after an internal approval…

    29 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Enable Metadata Cascading when using the Add Metadata outcome

    Description

    Allow users to enable metadata cascading when applying the Add Metadata outcome to a folder. This should be a user-selectable option in the workflow builder (for example, a simple "Enable metadata cascading" checkbox for this outcome).

    Business Value

    Many document-centric processes follow the same pattern:

    • A user submits a request through a form.
    • A workflow automatically creates a dedicated folder for that request.
    • Documents related to the request are uploaded into that folder over time by multiple users.

    While workflows can already create the folder and assign metadata to it, there is currently no way to enable metadata cascading…

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. We want to apply classification labels using Automate without granting Editors permission to change labels

    In Relay, we had a workflow where users would manually trigger a workflow, assign an approval task, and upon approval, automatically change or assign a classification label. This was done to assign a label indicating that the content is ready for public release, enabling external sharing.

    However, this cannot be achieved with Automate workflows. Upon checking the specifications, we found that unless the Admin Console allows Editors to modify classification labels, Automate workflows cannot assign labels. In our organization, we have only permitted Co-owners and Owners to change labels. If we allow Editors to change labels, general employees would be…

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Reference loop variables in a conditional branch within the loop in Box Automate workflow

    In a Box Automate workflow, when looping through files, we need to be able to run conditional checks on values/properties of the file within that loop.

    Potential use case: a user may want the workflow to ignore certain file types, or to only run Box AI Agent operations on certain files.

    Currently, many variables can be referenced within the "conditional split" element within a "loop" element, but not the loop variables themselves.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. I’d like the workflow error messages to include specific details about what the problem is.

    Now that BoxAutomate has been released, I’m really excited about all the new possibilities it will unlock inside Box.
    However, with the current specifications, when an error occurs in a workflow, a message is displayed, but it doesn’t tell us what exactly went wrong.
    With things the way they are, it’s impossible for us to fix the workflow on our own. It’s like being told, “Something’s broken… somewhere… good luck!”
    To enable users to fix errors by themselves, we’d like the error messages to clearly specify the detailed points where the problem occurs

    ワークフローでエラーが発生した場合、メッセージが表示されるが、具体的にどこが問題なのかが分からないです。
    これではワークフローを自分たちで修正することもできません。
    ユーザーが自分でエラーを直せるように、エラーメッセージには詳細なポイントを明記してほしいと考えています。

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Box Automate: Local time zone support for date variables

    We use Box Automate to move files into daily folders.
    Because date/time variables are evaluated in UTC, workflows that run around local midnight (for example in JST) sometimes create folders with the previous day’s date.
    We would appreciate it if you could add the following configuration options for the date/time variables used in folder and file names:

     (1) Ability to specify a time zone (e.g., Asia/Tokyo)
     (2) Ability to perform date/time arithmetic (e.g., adding +9 hours to UTC)


    <Box Automate:日付変数のローカルタイムゾーン対応の要望>

    Box Automate でワークフロー実行日ごとにフォルダを作成・振り分けています。
    現在は日付/時刻変数が UTC 基準で評価されるため、JST など UTC 以外の地域では深夜帯の実行時に前日の日付フォルダが作成されてしまいます。
    フォルダ名・ファイル名用の日付/時刻変数について、以下を設定できる機能をご検討いただけますと幸いです。
     
     (1) タイムゾーンの指定機能(例:Asia/Tokyo)
     (2) 日時演算機能(例:UTC に +9 時間)

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. "File that triggered the flow" variable is unavailable in Box Automate.

    In Box Automate, when implementing a process triggered by a file request and selecting "Move" as the "File Action," the "File that Triggered the Flow" variable is unavailable as the file to be moved.

    This variable is available in Box Relay and can be used for purposes such as distributing the triggered file to a specified folder.

    Without this variable, Box Automate is clearly inferior to Box Relay.

    We hope that the "File that Triggered the Flow" variable will be made available soon.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Increase the Maximum Number of Actions per Box Automate Workflow

    {English}
    We would like to request an increase in the maximum number of actions that can be executed within a single Box Automate workflow.

    Currently, the limit is 200 actions per workflow execution. However, based on real customer business requirements, some workflows are reaching this limit and cannot be fully implemented within the current constraints.

    Increasing the limit to approximately 2,000 actions would address these use cases and enable customers to automate larger-scale business processes without requiring complex workarounds or workflow redesign.

    This request was submitted based on customer feedback.

    ====
    {Japanese}
    Box Automateワークフローで一度に実行できるアクション数の上限拡張を希望します。

    現在、1回のワークフロー実行で利用できるアクション数は200に制限されています。しかし、実際の顧客業務要件を考慮すると、この上限に達してしまい、実現できないフローが存在します。

    上限を2,000アクション程度まで拡張いただけると、このようなユースケースに対応でき、大規模な業務プロセスをワークアラウンドや複雑なフロー分割なしで実装できるようになります。

    本要望は顧客からのフィードバックに基づくものです。

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Allow for Duplication of Automate Workflows and Creation of Automate Templates

    Currently, Relay has the ability to duplicate workflows, but Automate does not. We can also create templates for Relay workflows, but not for Automate. Automate should have the same capabilities.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Workflow Management Report

    The new Automate features are much more powerful than the previous Relay, and I’m excited to start using them going forward. After enabling Automate, I expect many users will create workflows, so the number of workflows in a tenant will increase significantly.

    Currently, I can visually check the workflows created in a tenant from the admin console, but as the number of workflows grows, it becomes difficult to review them all and properly manage them.

    It would be very helpful to have a way to export or list all workflows that exist in a tenant.

    Example fields:
    Workflow name
    Creator…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Enable Sharing Box Automate Workflows with User Groups

    Currently, Box Automate workflows can be shared with individual users. We would like to request an enhancement that enables workflows to be shared with user groups.
    This feature would reduce reliance on specific individuals and support team-based workflow management. In situations where the workflow owner leaves the company, changes roles, or becomes unavailable, other members of the group could continue to manage and maintain the workflow without disruption. This would improve operational continuity and reduce administrative overhead.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Loop through folders in a folder, and other lists of IDs/strings in a Box Automate workflow

    hi team. any thoughts on when we'll be able to loop through folders?

    (the ability to loop over files in a folder is good, and would be even better if we could have that within a loop that loops over folders)

    some use cases:

    • customers wanting to process files (i.e. move, rename, MDE) in folder trees, involving multiple levels of folders in the tree, and some but not all folders should be included excluded

    • customers wanting to bulk process folders - e.g. loop through folders in folders in folders, and then move/delete empty folders

    • loop through folders and validate certain…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. workflow notification send to groups

    Be able to send automation workflow notifications to groups instead of individual email addresses

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Request to Make Service Accounts Created During Box Automate Use Easier to Identify

    When a workflow is created and saved in Box Automate, a service account is created (e.g., InternalPlatformUser1234567ABCDEFGHIJ@boxdevedition.com).
    However, at present, it is difficult to determine whether this account was created as part of using Box Automate, making it hard to distinguish it from a suspicious user that may have been created maliciously.
    Therefore, we would like the service account (e.g., InternalPlatformUser1234567ABCDEFGHIJ@boxdevedition.com) to be made more easily identifiable as an account created for the use of Box Automate.
    For example, after a workflow is created in Box Automate, we would like a pop-up to be…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Allow api.box.com in Box Connectors for HTTPS Request steps in Automate workflows

    Please allow the HTTPS Request step in Box Automate to make requests to the Box API (api.box.com).

    There are many things not currently supported natively by Box Automate steps which could be solved if the HTTPS Request step/outcome were allowed to consume the Box API.

    For example:
    - generate Box access tokens
    - get file EXIF data from Box representations API
    - lock files
    - create shared links
    - get number of files in a folder
    - get file path
    - create shared link passwords
    - applying metadata cascade policies
    - metadata extraction on a group of files (rather than…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Expand Hubs actions for Box Automate to Enterprise and Enterprise Plus price plans

    to use workflows like "add file to a hub if it was added to a folder" Hubs actions should be available for all price plans that have Hubs enabled, i.e. Enterprise / Enterprise Plus and Enterprise Advanced

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Box Automate  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. generate folder uploaAdd an action to generate an email upload address for a folder in Box Automated email address

    We would like Box Automate to provide a folder action that enables email uploads for a specified folder and generates or retrieves the folder's email upload address.

    Currently, email uploads must be enabled manually in the settings of each folder. This becomes time-consuming when folders are created dynamically or when the same configuration must be applied to many folders.

    For example, we would like to create the following workflow:

    1. Create a new folder through Box Automate.
    2. Enable email uploads for the newly created folder.
    3. Generate or retrieve the folder's email upload address.
    4. Store the email address in metadata, send it…
    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Signer Verification in Box Automate

    Request to have a configurable option in an automate workflow to require a pre-defined signer verification method when sending a signature request from automate. Ex: Form is submitted, document is generated, document is sent for signature and user is required to sign with CAC/PIV card, use 2FA, etc.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1
  • Don't see your idea?