Slack notifications are matched to a user’s Slack account by email — if the email on the Fibery account and the email on the Slack account don’t match exactly, notifications don’t arrive in Slack. In our org, Slack was adopted before Fibery and the Slack owner hasn’t been able to change their Slack email.
Right now the only way around this is to replicate native notification behavior manually with automation rules — a “Send Message to Channel” Slack action triggered on mention or assignment. But automation rules are scoped to a single database, so getting the same coverage a working native integration would give for free means building and maintaining a separate rule per database the affected person needs to be notified from.
Ask: Either of these would ease the burden — letting a Fibery account link to Slack without requiring matching emails, or exposing notification data via the API so custom apps could surface it directly so we can consolidate all of the areas where people are commonly working.