Embedding Pickaxe into Client CRM via API - Best Practices?

General
1

Hey everyone! Looking to learn from anyone who’s done deeper integrations with Pickaxe.

I’m exploring embedding a Pickaxe into a client’s private CRM using the external API/embed approach, and trying to clarify the best architecture.

Key questions:

  1. How does the embedded experience typically show up?

    1. Does it function more like:
      1. a chatbot interface inside the CRM
      2. a triggered function (e.g. “analyze this record”)
      3. or something else entirely?
    2. Authentication & access: If the CRM is behind a login wall, how are you handling this in practice?
      1. Are you passing user/session data into Pickaxe via API?
      2. Or is the Pickaxe operating as a separate layer with its own auth?
    3. Data flow & security: In your setups, are you:
      1. pulling CRM data → sending it to Pickaxe for processing → returning outpuT
      2. or embedding Pickaxe more directly into the environment?
    4. Deployment model: Have you found more success with:
      1. full API-based integration into the CRM
      2. vs embedding a UI (iframe/widget-style)

Context: Use case is building an AI assistant that reviews CRM data and generates actionable recommendations (sales insights, workflow flags, etc.). Goal is to make it feel native to the CRM - not like a separate tool.

Appreciate any insights I am not a technical consultant and new to using the pickaxe API function.