Skip to content
picrm
Create account

Integrations

Bring customer context in. Keep every connection scoped.

Connect Google, Microsoft, and Slack to your workspace, then choose which products can use each account. Reading customer context and sending messages stay separately controlled.

Create accountSee trust & controls

One connection, from evidence to a held draft

Representative · changes nothing

  1. Selected evidence

    Gmail · renewal thread

    The buyer asked for a revised renewal plan.

    A reviewer pinned this exact message. The run fetches it only when needed and refuses it if the content changed.

  2. CRM outcome

    Task · Northstar Labs

    Prepare renewal options by Thursday.

    The run records the accountable next step beside the selected provider source in its receipt.

  3. Outbound held

    Email draft · awaiting approval

    Confirm the revised renewal plan.

    The exact recipient, subject, and body stay inside picrm until a teammate approves them.

The selected message can inform recorded CRM work without becoming permission to send the follow-up.

Representative product path. This public demonstration contacts no provider, changes no CRM record, and sends no message.

Supported connections

Each connection names what it can read, retain, and send.

Choose which products and reviewed agent versions can use each connection. picrm checks that access again before every run. Selected evidence, history sync, and outbound approval stay separate.

  • Workspace connectionGoogle WorkspaceGmail + Google CalendarSelected reads and optional history; Gmail sending needs separate consentExact boundaries
    Selected evidence
    A reviewer can pin exact Gmail messages or Calendar events. The run fetches only those items when it needs them and refuses content that changed after review.
    Customer history
    An administrator can separately enable bounded Gmail or Calendar history for customer records. That sync does not grant an agent provider access.
    Outbound boundary
    Gmail delivery needs separate send consent and approval of the exact recipient, subject, and body.
  • Workspace connectionMicrosoft 365Outlook + Microsoft CalendarSelected reads and optional history; no outbound deliveryExact boundaries
    Selected evidence
    A reviewer can pin exact Outlook messages or Calendar events. The run fetches only those items when it needs them and refuses content that changed after review.
    Customer history
    An administrator can separately enable bounded Outlook or Calendar history for customer records. That sync does not grant an agent provider access.
    Outbound boundary
    Read only. picrm does not send email through Microsoft 365.
  • Workspace connectionSlackChannels + peopleOne pinned destination; posting needs exact-message approvalExact boundaries
    Pinned destination
    A reviewed agent version pins one destination from the workspace's indexed channel and people list.
    Outbound boundary
    A teammate approves the exact destination and message before picrm posts it.
  • Product mailboxZoho MailOAuth mailboxOptional bounded history sync; sending needs exact-message approvalExact boundaries
    Customer history
    An administrator decides whether to sync inbox history and how far back to look. Bounded plain-text summaries can enter customer history; this does not give an agent inbox access.
    Outbound boundary
    Every agent email starts as a draft and needs approval of the exact recipient, subject, and body.
  • Product mailboxAgentMailOne scoped inboxNew inbound only, with no backfill; sending needs exact-message approvalExact boundaries
    Customer history
    One product receives the scoped inbox. New signed inbound messages can enter customer history; existing mail is not backfilled and an agent gets no inbox access.
    Outbound boundary
    Every agent email starts as a draft and needs approval of the exact recipient, subject, and body.
  • Product senderpicrm outboundManaged senderOutbound only after approval; no inbox or history syncExact boundaries
    Inbound access
    There is no inbox to read or sync. This option only carries a draft out of picrm after approval.
    Outbound boundary
    A teammate approves the exact recipient, subject, and body before delivery.

Disconnecting a provider blocks new use of that capability. Customer records, deals, tasks, and unrelated connections keep working.

picrm Founding

Connections are included. €49 per workspace, each month.

Create the workspace without a card, then connect only the accounts each product needs.

Create accountRead trust & controls