Integration

NinjaPipe integration

NinjaPipe CRM: list, read, create, update and delete contacts, companies, deals, products, budgets, orders, projects and project tasks; list and add contact timeline activities (notes, tasks) and budget expenses; list and create CRM lists and add a contact or company to one; list, read, create, update and delete pipelines, list and add pipeline items (cards); list the workspace members. Not exposed: client portal access (its answer returns a generated password), workspace-level general tasks, task reordering, and the single-record, update and delete routes of activities, budget expenses, lists, list members and pipeline items. Authentication is a NinjaPipe API key (np_...) sent as a Bearer token; the key names its workspace.

Connect NinjaPipe How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in NinjaPipe.Built from the 55 NinjaPipe tools below, on the connection you add once.

What you can do with NinjaPipe

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Budget, 5 operations

create_budgetCreate budgetPOSTCreate a new budget in your workspace. Budgets help track financial planning and spending across different categories and periods. The budget name and allocated amount are required. You can optionally set the category, period, status, and date range.
delete_budgetDelete budgetDELETEPermanently delete a budget from your workspace. This action cannot be undone. The budget must exist and belong to your workspace. You will receive confirmation of the deletion.
get_budgetGet budgetGETRetrieve a specific budget by its ID. Returns complete budget information including financial details and metadata. The budget must exist and belong to your workspace. Returns 404 if the budget is not found.
list_budgetsList budgetsGETRetrieve a paginated list of budgets with optional filtering and search capabilities. You can filter budgets by status, category, period, and search across name and description fields. Results are paginated with a maximum of 100 budgets per page.
update_budgetUpdate budgetPUTUpdate an existing budget. You can modify any budget field including name, allocated amount, status, category, and date range. Only provided fields will be updated. The budget must exist and belong to your workspace.

Company, 5 operations

create_companyCreate companyPOSTCreate a company. Requires API key write permission.
delete_companyDelete companyDELETEPermanently deletes the company (same as the app UI). Linked contacts are unlinked first. Subsequent GET by ID returns 404.
get_companyGet companyGETGet one company by ID. Returns 404 if the company was deleted or archived.
list_companiesList companiesGETLists the companies of the workspace, one page at a time (page, limit), with an optional text search. Archived companies are excluded.
update_companyUpdate companyPUTUpdates a company: name, status, industry or website. Send only the fields you want to change.

Contact, 5 operations

create_contactCreate contactPOSTCreate a new contact in your workspace. At least one name field (first_name or last_name) is required. Email addresses must be unique within your workspace.
delete_contactDelete contactDELETEPermanently delete a contact from your workspace. This action cannot be undone. The contact must exist and belong to your workspace. You will receive confirmation of the deletion.
get_contactGet contactGETRetrieve a specific contact by its ID. The contact ID must be a valid UUID format. The response includes the contact's details along with associated owner and company information.
list_contactsList contactsGETRetrieve a paginated list of contacts with optional filtering and search capabilities. You can filter contacts by status, owner, assignee, and search across name, email, and phone fields. Results are paginated with a maximum of 100 contacts per page.
update_contactUpdate contactPUTUpdate an existing contact. You can update any field by including it in the request body. If updating the email address, it must be unique within your workspace. Only provided fields will be updated. Unrecognized body fields return HTTP 400.

Deal, 5 operations

create_dealCreate dealPOSTCreate a new deal in your workspace. Deals represent sales opportunities with associated contacts and companies. The deal name is required. You can optionally set the value, status, and associate it with contacts and companies.
delete_dealDelete dealDELETEPermanently delete a deal from your workspace. This action cannot be undone. The deal must exist and belong to your workspace. You will receive confirmation of the deletion.
get_dealGet dealGETRetrieve a specific deal by its ID. Returns complete deal information including associated contact and company details. The deal must exist and belong to your workspace. Returns 404 if the deal is not found.
list_dealsList dealsGETRetrieve a paginated list of deals with optional filtering and search capabilities. You can filter deals by status, owner, and search across name fields. Results are paginated with a maximum of 100 deals per page.
update_dealUpdate dealPUTUpdate an existing deal. You can modify any deal field including name, value, status, priority, and associated contacts or companies. Only provided fields will be updated. The deal must exist and belong to your workspace.

Order, 5 operations

create_orderCreate orderPOSTCreate an order. Requires orders:create (session) or API key write. Put line items, currency, and custom fields in settings_json (same shape as the app).
delete_orderDelete orderDELETEPermanently delete an order. Requires orders:delete or API key write.
get_orderGet orderGETFetch one order by ID within your workspace.
list_ordersList ordersGETRetrieve a paginated list of orders in the workspace. Matches the Orders page in the app (line items and currency live in settings_json). Requires orders:read (session role) or API key read.
update_orderUpdate orderPUTPartial update. Send only fields to change. Use settings_json for line items and currency.

Pipeline, 5 operations

create_pipelineCreate pipelinePOSTCreate a pipeline. Requires name, pipeline_type (contacts | companies | deals | general), and at least one stage object { id, name, color }.
delete_pipelineDelete pipelineDELETEPermanently deletes the pipeline and all of its items (cards). Matches the app Danger zone delete pipeline action.
get_pipelineGet pipelineGETGet one pipeline by ID, including stages and settings.
list_pipelinesList pipelinesGETLists the pipelines of the workspace with their stages and settings, one page at a time (page, limit). The reference mentions type, archived and slug filters without naming their parameters, so they are not exposed.
update_pipelineUpdate pipelinePUTUpdates a pipeline: name, description, slug or stages. Send only the fields to change.

Product, 5 operations

create_productCreate productPOSTCreate a new product in your workspace. Products represent items or services in your catalog with pricing and inventory information. The product name and SKU are required.
delete_productDelete productDELETEPermanently delete a product from your workspace. This action cannot be undone. The product must exist and belong to your workspace. You will receive confirmation of the deletion.
get_productGet productGETRetrieve a specific product by its ID. Returns complete product information including settings and metadata. The product must exist and belong to your workspace. Returns 404 if the product is not found.
list_productsList productsGETRetrieve a paginated list of products with optional filtering and search capabilities. You can filter products by status, category, product type, and search across name, description, and SKU fields.
update_productUpdate productPUTUpdate an existing product. You can modify any product field including name, price, status, category, and settings. Only provided fields will be updated. The product must exist and belong to your workspace.

Project, 5 operations

create_projectCreate projectPOSTCreate a project. Requires tasks create permission (session) or write permission (API key).
delete_projectDelete projectDELETEDeletes the project and its tasks (database cascade). Requires delete permission on tasks for session auth.
get_projectGet projectGETFetch one project by ID. The project must belong to your workspace.
list_projectsList projectsGETRetrieve a paginated list of projects in the workspace. Matches the Projects & Tasks feature in the app. With a NinjaPipe API key (np_), the workspace is implied by the key.
update_projectUpdate projectPUTPartial update. Send only fields to change. You may update settings_json (for example link a contact).

Task, 5 operations

create_project_taskCreate project taskPOSTCreate a task or subtask. Optional parent_id must reference another task in the same project.
delete_project_taskDelete project taskDELETEDelete a task. Child tasks may cascade per database rules.
get_project_taskGet project taskGETFetch a single task within a project.
list_project_tasksList project tasksGETReturns a flat list of tasks for the project. Use parent_id to build a tree in your client. For workspace-level tasks not tied to a project, see List General TasksList General Tasks.
update_project_taskUpdate project taskPUTUpdate any task fields. Setting parent_id to an invalid or cyclic parent returns 400 or 409 (TASK_PARENT_CYCLE).

Activity, 2 operations

create_contact_activityCreate contact activityPOSTCreate a note or a task on a contact's timeline: set type to note or task. A task also creates a project task linked to the activity, so updating that task with update_project_task keeps the activity in sync.
list_contact_activitiesList contact activitiesGETList timeline activities for a contact (notes and tasks). Optional query type=note,task filters results. Requires read permission.

Expense, 2 operations

create_budget_expenseCreate budget expensePOSTCreate a new expense for a specific budget. The expense will be automatically added to the budget's spent amount. The budget must exist and belong to your workspace. The expense amount cannot exceed the remaining budget allocation.
list_budget_expensesList budget expensesGETRetrieve a paginated list of expenses for a specific budget with optional filtering and search capabilities. You can filter expenses by category and search across description and category fields.

Item, 2 operations

create_pipeline_itemCreate pipeline itemPOSTAdd a card to a pipeline. Requires title and stage_id.
list_pipeline_itemsList pipeline itemsGETList cards in a pipeline. Optional query: stage_id to filter by stage.

List, 2 operations

create_listCreate listPOSTCreate a list. Requires lists:create or API key write.
list_listsList listsGETRetrieve CRM lists (Contact or Company) in the workspace with pagination. Requires lists:read (session) or API key read.

Member, 2 operations

add_to_listAdd to listPOSTAdd a contact or company to a CRM list in your workspace. The list must already exist and must be the correct type: use contact_id for Contact lists and company_id for Company lists. Requires lists:create (session) or API key write.
list_workspace_membersList workspace membersGETReturns active workspace members for the workspace tied to your API key. Use account_id when setting contact assigned_to, deal owner_id, or pipeline assignees. Requires read permission on the API key. Results are workspace-scoped only.

Use NinjaPipe from Claude Code, Cursor or Codex

Connect NinjaPipe in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its NinjaPipe operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect NinjaPipe

Create your workspace
Sign up free. Nothing to install.
Connect NinjaPipe once
Add your NinjaPipe connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.