ExPipedrivePhoenix

Optional Phoenix helpers for Pipedrive marketplace OAuth install (authorize redirect + callback). Token exchange and TokenStore live in core ex_pipedrive (GitHub).

This package is independent of Überauth. If you already use ueberauth_pipedrive, keep it; otherwise this is the first-party install path that stores ExPipedrive.Oauth.Token via your TokenStore.

Core OAuth remains usable without Phoenix.

Installation

def deps do
  [
    {:ex_pipedrive, "~> 0.2.0"},
    {:ex_pipedrive_phoenix, "~> 0.1.1"}
  ]
end

Minimal install flow

defmodule MyAppWeb.PipedriveController do
  use MyAppWeb, :controller
  use ExPipedrivePhoenix.Install,
    token_store: MyApp.PipedriveTokenStore,
    tenant_assign: :current_account_id,
    success_to: "/settings/pipedrive",
    error_to: "/settings/pipedrive?error=1"
end

# router.ex
scope "/pipedrive", MyAppWeb do
  pipe_through [:browser, :require_authenticated_user]
  get "/install", PipedriveController, :authorize
  get "/callback", PipedriveController, :callback
end

# config/runtime.exs
config :my_app, ExPipedrivePhoenix,
  client_id: System.fetch_env!("PIPEDRIVE_CLIENT_ID"),
  client_secret: System.fetch_env!("PIPEDRIVE_CLIENT_SECRET"),
  redirect_uri: "https://app.example.com/pipedrive/callback"

authorize/2 stores a CSRF state in the session and redirects to Pipedrive. callback/2 verifies state, exchanges the code, and TokenStore.put/2s the token for conn.assigns[tenant_assign] (or a literal :tenant_id option).

Pass :otp_app (default :ex_pipedrive_phoenix) if config lives under another app key.

Version coupling

If you clone this repo next to ex_pipedrive, Mix uses a path dependency on core. CI and Hex consumers use {:ex_pipedrive, "~> 0.2"}.

HEX_PUBLISH=1 mix hex.publish

Hex: ex_pipedrive_phoenix.

Development

mix deps.get
mix test
mix format --check-formatted
mix credo --strict