Update on Slack API Changes: Important Actions Required for uipath.slack.activities βœ…

Greetings,

We want to inform you about an important change that affects the file upload functionality within the uipath.slack.activities package, commonly referred to as Classic Slack Activities. Slack has introduced breaking changes to their file upload APIs, which will impact how files are attached to messages or replies.

Details of the Change: Slack has announced that the existing APIs used for uploading files will be deprecated and be sunset on Tuesday, 11th of March. More details about this change can be found on Slack’s official announcement here.

Impact Assessment

  • Customers using Integration Service (IS) Slack Activities: There is no impact. Our engineering team will deploy a fix in production on 10th of March to ensure seamless functionality continues.
  • Customers using uipath.slack.activities: If you are uploading files to Slack through the activities from this package, this functionality will cease to operate starting from 11th of March.

Important Compatibility Information:

  • For users of v1.0.3 or v1.1.0: It is crucial to update to version v1.1.1 only, to avoid introducing breaking changes found in the v2.x.x versions.
  • For users of v2.0.0 or v2.0.1: You should update to version v2.0.2 which includes all necessary updates for modern projects.

Immediate Actions Required: To address this, we have released updated versions of the uipath.slack.activities package in the official UiPath feed. The updates, available in versions v2.0.2 for modern projects and v1.1.1 for classic projects, are crucial to ensure continuity in your automations that involve file uploads to Slack.

Steps to Take:

  1. Update Your Activities: Depending on your current version, please update the uipath.slack.activities package in all automations that upload files to Slack from the official UiPath feed to either v1.1.1 or v2.0.2 as applicable. This update is necessary to align with the new API standards set by Slack and to avoid disruptions in your workflows.
  2. Monitor Your Automations: After updating, ensure to test and monitor your automations to verify that all functionalities are operating as expected.

Note on Version Compatibility: Please be aware that transitioning from any v1.x.x version to v2.x.x could introduce breaking changes to your existing workflows.

We understand that updating dependencies can require some effort, especially across multiple projects. We are committed to supporting you through this process and minimizing any inconvenience.

Support: Should you have any questions or need assistance during this transition, please feel free to reach out through this forum or contact our support team directly.

Thank you for your prompt attention to this matter and for your continued cooperation.

2 Likes