Send selected Foundbase events to Slack channels
Connect a Slack workspace to a Foundbase project. Choose which changes should trigger a message and send them to a default channel or a separate channel for each event.
Connect a Slack workspace to a Foundbase project. Choose which changes should trigger a message and send them to a default channel or a separate channel for each event.
The Slack integration sends outbound messages from Foundbase to channels in a connected Slack workspace. It supports predefined product events and a selected action inside a workflow.
Or
The Slack integration sends outbound messages from Foundbase to channels in a connected Slack workspace. It supports predefined product events and a selected action inside a workflow.
In the integration settings, the team chooses which events are active. Each event can use its own channel. If no separate channel is selected, Foundbase uses the default channel.
Predefined events come from tasks, pipeline subjects, contacts, companies and follow-ups. Messages are built from the data available on each record and can link back to Foundbase.
The integration does not update Foundbase records from Slack and does not provide search or commands inside Slack. The documented direction is from Foundbase to Slack. Delivery depends on the selected setup and a valid Slack connection.
These examples show possible configurations using the documented events and workflow actions. They are not customer cases or outcome promises.
Enable the pipeline subject stage-change event and select the channel that should receive the standard message.
Send created or updated tasks to a project channel. The message can show fields such as status, assignee, priority and due date.
Enable the overdue follow-up event and use the default channel or a separate channel for this event.
Add Slack as a workflow action and set the channel and message. The action runs only when the workflow reaches this step.
Slack sends messages out of Foundbase. Calendar, email and telephony integrations have separate pages for their direction and setup.
Customer testimonials
The statement below is about Foundbase generally and does not verify results from the Slack integration.

I have been looking for the right functional and user-friendly tool that can help with everything from project management, financial management, sales work, etc. The answer to this is Foundbase.
Tasks can send a message when they are created, updated or deleted. Pipeline subjects also support stage changes. Contacts and companies can send messages on creation, updates and deletion.
Follow-ups can send messages when they are created, updated, deleted or overdue. The team selects active events in the project Slack settings.
A message is sent only when Slack is connected to the project, the event is enabled and a channel can be resolved from the event routing or default channel.
Foundbase retrieves public and private channels visible to the connected Slack installation. The team selects a default channel in the integration settings.
Each of the 17 events can also use a separate channel. The event-specific channel takes precedence. Otherwise, Foundbase uses the default channel.
This routing can keep task and pipeline changes in different channels without claiming that Slack automatically evaluates or prioritises messages.
The content depends on the event. A task message can include title, assignees, status, priority, due date and a short description. Pipeline messages can include pipeline, stage, value, company and assignee.
Contact, company and follow-up messages use relevant fields available on the record. When the event provides a URL, the title links back to Foundbase.
Messages provide orientation. Work on the record continues in Foundbase.
Predefined integration events send a standard message when a selected record type changes. They are controlled by the enabled events and channel routing in the Slack settings.
The workflow action sends custom text to the channel selected in the workflow. It runs only when the rest of the workflow reaches the Slack action.
The practical effect depends on the events, channels and working process the team configures.
The Slack page owns questions about message types, channel routing and direction. The underlying product pages explain the work that creates those events.
See the platform in action and get a quick overview of the core workflows.



We're always ready to show you what Foundbase can do. You're also always welcome to visit our lovely office in Odense, Denmark
Connect Slack, choose events and channels, and review the setup in the integration settings.
Predefined events cover tasks, pipeline subjects, contacts, companies and follow-ups. Events include creation, updates and deletion, plus stage changes and overdue follow-ups where supported.
Yes. You can select a default channel and then set a separate channel for each event. The separate channel is used first, with the default channel as fallback.
Yes. Slack can be selected as a workflow action with a channel and message. It sends only when the workflow trigger and any conditions lead to that action.
No. The documented integration sends messages from Foundbase to Slack. It does not provide commands for searching or updating Foundbase records from Slack.
Foundbase records the latest send status and error on the Slack connection. Delivery requires an active connection, valid access and a channel the integration can post to.
No. The team selects active events and channels. A workflow message also requires a configured workflow that reaches the Slack action.