cogny clicrmfirst 15 calls free
upsales queried from the terminal.
List accounts, contacts, opportunities, orders, activities and campaigns from your Upsales CRM — from Bash over the Upsales MCP. Pull the pipeline as JSON for weekly signals, forecasting, and sales-velocity reporting.
- 1. sign up, free for the first calls (uses your git email)
npx @cogny/cli init --agent claude-code - 2. see every Upsales tool
cogny tools list - 3. call any tool from bash, no MCP wiring
cogny tools call mcp__Upsales__list_opportunities --input '{…}'
Building a weekly pipeline review in Upsales means assembling views and exporting per object. The CLI returns accounts, opportunities, and activities as JSON in one call you can schedule and roll up. Connect Upsales once in Cogny Solo and let your coding agent, or a scheduled loop, do the querying for you.
Start SoloSign yourself up with one command. The CLI issues a key, wires nothing, and exposes every Upsales tool over JSON-RPC. The first 15 calls are free.
npx @cogny/cli init --agent claude-code
real Upsales tools.
Tool names as the Upsales MCP serves them. Send --input JSON, get JSON back. The payloads are illustrative.
- mcp__Upsales__list_opportunities
List open pipeline (orders with probability < 100).
cogny tools call mcp__Upsales__list_opportunities \ --input '{"limit":2,"sort":"-date"}'
example response
{ "data": [ { "id": 88121, "description": "Acme — Platform Q3", "value": 240000, "probability": 60, "stage": { "name": "Proposal" }, "client": { "name": "Acme AB" } }, { "id": 88119, "description": "Beta — Renewal", "value": 96000, "probability": 80, "stage": { "name": "Negotiation" }, "client": { "name": "Beta HB" } } ], "metadata": { "total": 47, "limit": 2, "offset": 0 } } - mcp__Upsales__list_accounts
List accounts (companies/customers).
cogny tools call mcp__Upsales__list_accounts \ --input '{"limit":2,"sort":"name"}'
example response
{ "data": [ { "id": 5001, "name": "Acme AB", "orgNo": "556677-8899", "users": [ { "name": "Lena R." } ] }, { "id": 5002, "name": "Beta HB", "orgNo": "559900-1122", "users": [ { "name": "Omar S." } ] } ], "metadata": { "total": 1203, "limit": 2, "offset": 0 } } - mcp__Upsales__list_activities
List sales activities (calls, tasks, to-dos).
cogny tools call mcp__Upsales__list_activities \ --input '{"limit":2,"sort":"-date"}'
example response
{ "data": [ { "id": 77010, "description": "Discovery call", "date": "2026-06-15", "closeDate": null, "users": [ { "name": "Lena R." } ], "client": { "name": "Acme AB" } }, { "id": 77008, "description": "Send proposal", "date": "2026-06-14", "closeDate": "2026-06-14", "users": [ { "name": "Omar S." } ], "client": { "name": "Beta HB" } } ], "metadata": { "total": 612, "limit": 2, "offset": 0 } }
the rest of the surface.
A sample of the other Upsales tools. Run cogny tools list --json for every tool and its input schema.
- mcp__Upsales__get_account
- mcp__Upsales__list_contacts
- mcp__Upsales__get_contact
- mcp__Upsales__list_orders
- mcp__Upsales__list_appointments
- mcp__Upsales__list_agreements
- mcp__Upsales__list_campaigns
- mcp__Upsales__list_leads
- mcp__Upsales__query
calls from a script. verdicts from cogny.
Every write is logged with who authorised it. Launches your agent makes (a new campaign, a new ad) become measured tickets automatically; for other changes, your agent offers to register them. Cogny measures each in your own data, three days later for ads and seven for content and SEO, and closes it as worked, partial, didn't work or inconclusive.
- worked
Moved the number. Every measured win has a share card.
- partial
Some of it did.
- didn't work
On the record anyway, so it isn't proposed again.
- inconclusive
Not enough data to call.
questions.
- Is this an official Upsales CLI?
- No — it is the Cogny CLI calling the Upsales MCP over the cogny-mcp-proxy. You connect your Upsales API token once in Cogny, then read CRM objects from Bash. Upsales Technology AB is not affiliated.
- How do I query an object the named tools do not cover?
- Use the `query` escape hatch — it runs a GET against any Upsales v2 list resource by name with the same limit/offset/sort/filters arguments, so you are not limited to the pre-named list tools.
- What reports can I build?
- Weekly pipeline signals from `list_opportunities`, activity volume from `list_activities`, and account/contact rollups — pulled as JSON on a schedule and summarized by an agent.
Building an agent? The full tool map for every server is one fetch: /cli/llms.txt