Close out Slack conversations for finished Bitly campaigns
When your campaign process marks a launch complete, archive its Slack conversation to keep active work easier to scan while retaining its history.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Archive a Slack conversation
Archives a slack conversation by its id, rendering it read-only and hidden while retaining history, ideal for cleaning up inactive channels; be aware that some channels (like #general or certain dms) cannot be archived and this may impact connected integrations.
Why this helps
Old campaign conversations crowd active Slack spaces long after their links are no longer being worked on.
- Reduce clutter from completed campaign conversations.
- Retain channel history after archiving.
- Tie channel cleanup to a supplied completion signal.
Setup
Build it in a few focused steps.
- 1Connect Bitly and Slack once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis to create it from any channel.
- 3Describe the outcome in one instruction: archive the Slack conversation identified in the webhook request when the campaign is complete.
- 4Choose the Notis webhook trigger and where run reports should go.
- 5Test with one completed campaign conversation you are allowed to archive.
Questions about this workflow
Does archiving delete the conversation?
No. The listed action archives a conversation, making it read-only and hidden while retaining history.
Does Bitly automatically tell Notis a campaign is complete?
No Bitly trigger event is available. Your campaign process must send the completion signal and conversation ID to the webhook.
Can every Slack conversation be archived?
Some channels or direct messages may not be archivable. The action can also affect connected integrations, so use the supplied conversation deliberately.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bitly to Slack. A trigger fires from one place; an action lands in another.
Bitly triggers
Slack actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Set snooze duration
Deprecated: turns on do not disturb mode for the current user, or changes its duration. use `set dnd duration` instead.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add a custom emoji to a Slack team
Deprecated: adds a custom emoji to a slack workspace given a unique name and an image url. use `add emoji` instead.
Add an emoji alias
Adds an alias for an existing custom emoji in a slack enterprise grid organization.
Add a remote file
Adds a reference to an external file (e.g., google drive, dropbox) to slack for discovery and sharing, requiring a unique `external id` and an `external url` accessible by slack.
Add a star to an item
Stars a channel, file, file comment, or a specific message in slack.
Add call participants
Registers new participants added to a slack call.
Add emoji
Adds a custom emoji to a slack workspace given a unique name and an image url; subject to workspace emoji limits.
Add reaction to message
Adds a specified emoji reaction to an existing message in a slack channel, identified by its timestamp; does not remove or retrieve reactions.
Connect any two apps with Notis in the middle.
Bitly and Slack, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Slack.