How to Set Up Slack Integration

Yes. Map the channel to a company or a deal with '/lumo sync here to company <name>', or on the Channel sync tab of the Slack settings page. Its messages then appear on that record's timeline under a Slack tab, in the record's Conversations widget, and as evidence Lumo can cite. Lumo has to be invited to the channel first with /invite @Lumo, private channels included.

New messages arrive within seconds. A newly mapped channel also pulls the last 90 days in the background, and '/lumo history' asks for everything instead. Slack caps that pace at roughly 900 messages an hour for an app distributed the way ours is, so a channel with tens of thousands of messages genuinely takes hours. That is the limit, not a stalled job.

'/lumo sync', '/lumo status', '/lumo history', '/lumo unsync' and '/lumo help' manage channel sync; everything except status is admin only because it writes CRM data the whole workspace can read. '/deal search <query>' and '/crm contact <query>' still search deals and contacts and return up to ten results each. Asking Lumo a free-text question from Slack is not switched on yet, and '/task new' does not create anything.

Eight, each an independent switch per channel: new deals, deal stage changes, deals won, deals lost, new activities, new tasks, tasks due, and tasks overdue. There are no value or stage filters on a subscription, so narrowing a channel means giving it fewer events.

Commands need your Slack member linked to a Lumenbase user, and linking is by email address only. An admin has to open Settings, Workspace, Integrations, Slack, Users and click Sync Users. If you still do not appear, your Slack profile email differs from your Lumenbase email, which is the only field matching compares.

No. The first notification about a record in a channel starts a message and every later notification about that same record posts as a reply under it, so one deal produces one thread. Threading is per channel, so the same deal in two channels keeps two threads.

No. Notifications are read-only and carry a link back into Lumenbase. Approvals, task completion, and stage changes happen in the app.

A Lumenbase workspace admin, who also needs permission to install apps in the Slack workspace. On Slack Enterprise Grid you may have to get the app approved by a Slack admin before the connection will complete.