New in Linkrium: Outlook, Instagram, Teams, LinkedIn & Calendar

Linkrium can now connect more of the places where individual conversations and follow-up already happen. Outlook email, Instagram direct messages, Microsoft Teams chats and LinkedIn messages can join the same contact-first inbox, while Outlook Calendar can mirror events beside Linkrium reminders and task deadlines.

These are five distinct connections, not one blanket Microsoft or social-media switch. Each has its own authorization method, supported message types and provider boundaries. Linkrium keeps the source visible so a message does not stop being an Outlook email or a Teams chat merely because it appears beside the same person's other history.

Quick answer#

The new release expands both sides of the follow-up loop: more conversations can enter the unified inbox, and dated work can move between Linkrium and Outlook Calendar.

Availability remains explicit. The supported-networks page shows which messaging connections the current deployment offers, and the connection screen checks the live backend catalog before presenting an account as connectable.

Outlook email in the person-based inbox#

Outlook is available as a mailbox provider inside Linkrium's Email channel. After Microsoft authorization, supported incoming and outgoing mail can appear in the same inbox as the contact's other synchronized conversations. Email keeps its subject, recipients, thread information and Outlook source label.

This is useful when a conversation moves between a quick message and a more formal email. Instead of treating the mailbox as a separate work queue, you can open the person, read the available context and reply through the connected Outlook mailbox. The existing Email integration overview explains the shared behavior and provider-dependent limits.

Outlook Mail does not grant access to Teams or Outlook Calendar automatically. It requests mail permissions for an Email connection, and those credentials are stored and refreshed for that purpose. This separation makes the permission boundary visible and lets you disconnect one Microsoft surface without silently removing the others.

Instagram DMs without another inbox tab#

Instagram now contributes supported one-to-one DMs to the Linkrium timeline. The current connection uses an existing signed-in Instagram browser session through the configured bridge. You do not type your Instagram password into Linkrium, but the session material is still sensitive and should be handled like a credential.

The release is deliberately narrower than Instagram itself. It covers one-to-one direct-message text that the bridge can synchronize. Group threads, story replies, reactions, edits, attachments and other richer events are not part of the current Linkrium milestone. Linkrium also cannot recover messages that the provider no longer exposes to the connected session.

Use the source badge before replying or acting on a message. A contact may have Instagram and email identifiers in the same Linkrium record, but each item keeps the provider it came from and uses that connected route for supported replies.

Microsoft Teams one-to-one chats#

The Teams connection uses its own Microsoft OAuth flow and is scoped to one-to-one chats. Supported text messages can be synchronized into a contact's history, and a text reply can go back through the Teams connection without opening a separate Teams tab.

Teams contains several conversation models, and this first release does not pretend they are interchangeable. Linkrium skips Teams channels, group chats and meeting chats because those conversations do not map cleanly to one person. Attachment-only messages, reactions, calls and other non-text events are also outside the supported scope.

That boundary keeps the contact-first model honest: when a Teams message appears in Linkrium, it represents a direct conversation with a specific counterpart. If your workflow depends on a channel post, a group decision or an attached file, continue to use Teams for that part of the conversation.

LinkedIn messages with clear session boundaries#

LinkedIn can now bring supported one-to-one direct messages into the same person-based history. Like Instagram, the current integration uses a handoff from an existing signed-in browser session rather than an official LinkedIn API. The connection screen explains how to capture the required session request and warns that the session remains tied to the browser context that created it.

Linkrium does not ask for or store your LinkedIn password. It also does not turn the connection into a prospecting or automation tool. Connect only an account you control, avoid spam or automated outreach and disconnect the session when it is no longer needed.

The synchronized scope is one-to-one DM text. Group conversations, reactions, edits, replies, attachments and other richer bridge events are skipped in this milestone. Treat the LinkedIn source label as the reliable boundary and return to LinkedIn when you need a native feature Linkrium does not expose.

Outlook Calendar closes the follow-up loop#

Messages often create work that belongs on a date: prepare for a call, send a proposal, revisit an unanswered question or keep a promise made in a chat. Outlook Calendar sync lets those dated commitments sit beside the conversation that created them.

When you connect Outlook Calendar, supported Outlook events are mirrored into Linkrium's calendar. Linkrium-owned reminders assigned to that calendar can be created remotely and updated on later syncs. Automatic sync runs on the configured cadence, and Calendar settings also provides a manual Sync now action.

Conflict behavior follows the event's origin. Outlook is authoritative for an event created in Outlook, so an edit made only to its Linkrium mirror may be replaced by the next sync. Change that event in Outlook to make the update persist. Linkrium-owned reminders are pushed outward, with provider conflicts surfaced instead of silently overwriting a concurrent remote edit. See conversation reminders and calendar for the full follow-up model.

Why Microsoft asks for three separate permissions#

Outlook Mail, Microsoft Teams and Outlook Calendar may use the same Microsoft identity, but they expose different data and actions. Linkrium therefore starts a separate consent flow for each connection:

1. Outlook Mail requests the permissions needed to read and send supported email.
2. Microsoft Teams requests the permissions needed for supported one-to-one chats.
3. Outlook Calendar requests the permissions needed to read events and synchronize Linkrium-owned reminders.

This is intentional. Connecting a mailbox should not silently grant calendar or Teams access, and revoking calendar access should not unexpectedly disconnect email. Review the permission screen for each connection and approve only the capability you intend to use.

One workflow across messages and calendar#

The value of the release is not simply a longer list of icons. It is the ability to keep a person's available context and the next action together.

A practical workflow looks like this:

1. Connect the accounts you control from Channels, then connect Outlook Calendar separately from Calendar settings.
2. Send a non-sensitive test message through each route you depend on and confirm the source, counterpart and timestamp in Linkrium.
3. Open a contact whose conversation spans more than one supported account.
4. Use cross-channel search to recover the message that created a commitment.
5. Reply through the appropriate connected account or create a task from the message.
6. Add a deadline or reminder and review it in Linkrium's calendar.
7. If it is assigned to Outlook Calendar, confirm the remote copy and edit Outlook-originated events in Outlook.

The original message remains the context for the action. That makes it easier to verify what was promised, which channel was used and where the follow-up belongs.

Connect carefully and verify the result#

Every connected account can expose private conversation data. Review how Linkrium handles connected message data, protect the workspace with strong authentication and remove accounts that are no longer needed.

For Microsoft connections, read the consent screen and remember that Mail, Teams and Calendar are separate. For Instagram and LinkedIn, use only your own signed-in browser session, keep copied session material out of notes and chat tools, and follow the provider's account rules. The bridge-based connections are not official provider APIs, so availability can change when a provider changes its web session or policies.

After connecting, test incoming synchronization, outgoing text replies, reconnect and disconnect behavior with non-sensitive data. Provider eligibility, plan limits, history depth and regional restrictions can still affect what a particular account can do.

With those boundaries understood, the new connections make Linkrium a more complete place to follow a person from conversation to action. Start free, connect the accounts marked available in your workspace and use Outlook Calendar when the next step needs a date.