Integration
Connect Pneumatic and Sellsy
When something happens in Pneumatic or Sellsy, your agent does the next thing in the other. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Pneumatic and Sellsy to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Pneumatic and Sellsy can do together
From Pneumatic to Sellsy
When Task Completed in Pneumatic
then Create Task in Sellsy
From Sellsy to Pneumatic
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Pneumatic and Sellsy
Triggers and actions 9 triggers · 18 actions
- Task Completed
Triggers when some task is completed.
- Task Returned
Triggers when a process is returned to this task.
- Workflow Completed
Triggers when a workflow is completed.
- Workflow Started
Triggers when a new workflow is started.
- Get Task
Get a single task by id.
- Get Template
Get a specific workflow template by id.
- List Templates
List all workflow templates in the account.
- List Users
List users in the account.
- Run Workflow
Run a New Workflow
- Update Task
Complete a task.
- New Company
Triggers when a new company (client or prospect) is created.
- New Contact
Triggers when a new contact is created.
- Updated Company
Triggers when a company (client or prospect) is updated.
- Updated Contact
Triggers when a contact is updated.
- Updated Task
Triggers when a task is updated.
- Create Annotation
Creates a new annotation.
- Create Company
Creates a new company (prospect or client).
- Create Contact
Creates a new contact.
- Create Opportunity
Creates an opportunity.
- Create Task
Creates a new Task.
- Create/Update Company
Creates a new company (prospect or client). Make an update if we found an existing company with provided email.
- Create/Update Contact
Creates a new contact. Make an update if we found an existing contact with provided email.
- Delete Task
Deletes a Sellsy task.
- Get Opportunity
Returns one Sellsy opportunity by id.
- Get Task
Returns one Sellsy task by id.
- List Opportunity Pipeline Steps
Lists the steps of a pipeline; supplies the required step id for Create Opportunity.
- Update Task
updates a task's title, description, due date, status etc.; fires task.updated.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Pneumatic
Pneumatic to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Pneumatic to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Pneumatic to StripeStripe is a payment processing platform for online businesses.
Pneumatic to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Pneumatic to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Pneumatic to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
More into Sellsy
HubSpot to SellsyHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to SellsyGoogle Sheets
Gmail to SellsyGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SellsyGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to SellsyGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Questions
Pneumatic and Sellsy, answered
What can start an automation from Pneumatic?
Any of Pneumatic's 4 triggers in the catalog, including Task Completed, Workflow Completed, Task Returned and Workflow Started. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Sellsy when something happens in Pneumatic?
Any of Sellsy's 12 actions, including Create Annotation, Create Company, Create Contact and Create Opportunity. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Sellsy to Pneumatic?
Yes. When something happens in Sellsy, your agent can act in Pneumatic too. This page covers both directions: Sellsy's triggers and Pneumatic's actions are listed here as well.
Do I have to build a connector for Pneumatic or Sellsy?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.