Integration
Connect Teamleader Focus to Spike.sh
When something happens in Teamleader Focus, your agent does the next thing in Spike.sh. 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 Teamleader Focus and Spike.sh 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 Teamleader Focus can start in Spike.sh
When New Company in Teamleader Focus
then Add alert rule in Spike.sh
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 Teamleader Focus and Spike.sh
Triggers and actions 5 triggers · 43 actions
- Deal Accepted
Triggers when a deal is accepted.
- Invoice Paid
Fires when a payment is registered on a Teamleader Focus invoice (vendor event invoice.paymentRegistered).
- New Company
Triggers when a new Company is added.
- New Contact
Triggers when a new contact is added.
- New Deal
Triggers when a new deal is created.
- Add invoice
Drafts a new invoice in Teamleader Focus.
- Add quotation
Creates a quotation on a Teamleader Focus deal.
- Add task
Create a task.
- Book Invoice
Books a draft Teamleader Focus invoice, giving it an invoice number and making it outstanding.
- Create Company
Creates a new company.
- Create Contact
Creates a new contact.
- Create Deal
Creates a new deal.
- Find Company
Returns up to 100 companies that match the specified search term, email, VAT number, tags or other criteria.
- Get company
Get details for a single company in Teamleader Focus.
- Get contact
Get a contact by id.
- Get deal
Get details for a single deal.
- Get Invoice
Returns one Teamleader Focus invoice with its customer, lines, totals and status.
- Get Task
Returns one Teamleader Focus task with its title, description, due date, work type and assignee.
- Link Contact to Company
Links an existing contact to an existing company, optionally setting the contact's position and whether they are a decision maker there.
- Update company
Update an existing company in Teamleader Focus. Only the fields you fill in are changed.
- Update contact
Update a contact.
- Update deal
Update a deal.
- Win deal
Marks a Teamleader Focus deal as won.
- Acknowledge incident
Acknowledge one or more Spike.sh incidents by counter id or incident id.
- Add alert rule
Create a new alert routing/automation rule with conditions and actions.
- Add escalation
Creates a new escalation policy for a Spike.sh team, defining who is notified, through which channel, and how long to wait between steps.
- Add integration
Create a new integration for a team (source system that sends alerts into Spike).
- Add on-call
Create a new on-call schedule for a team.
- Add service
Create a new service in a team, with name and description.
- Create Incident
Creates a Spike incident through one of your integrations and sends alerts. The integration decides which service and escalation policy the incident is routed to.
- Delete alert rule
Archives (soft-deletes) a Spike alert rule so it no longer applies to incoming incidents.
- Delete escalation
Archives (soft-deletes) a Spike escalation policy by its ID.
- Escalate incident
Escalates one or more Spike incidents to the next step of their escalation policy.
- Get escalation
Get escalation policy details by id.
- Get incident
Fetch a single incident by counter id.
- Get integration
Fetches an integration by its token, including its name, type, service, escalation settings and webhook URL. An error occurs if the integration is not found.
- Get service
Get a Spike service's details, along with its incidents and open-incident count.
- List alert rules
Lists all alert rules (enabled and disabled) configured for a Spike team.
- List escalations
Lists the escalation policies that belong to a Spike team.
- List incidents
Lists the incidents for a Spike.sh team.
- List on-calls
Lists the on-call schedules for a team.
- List services
Lists the services in a Spike team.
- List teams
Lists every team in your Spike organisation. Use a team's ID from here wherever other Spike actions ask for a team.
- Resolve incident
Resolve one or more incidents by counter id array.
- Update alert rule
Replace an existing Spike alert rule's name, conditions and actions.
- Update escalation
Replaces an existing escalation policy's name, steps and start delay. The whole policy is replaced, so send every step you want to keep.
- Update on-call
Updates an on-call schedule's name and/or moves it to another team. Rotations and layers are not changed by this action.
- Update service
Updates the name and/or description of an existing Spike.sh service.
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 Teamleader Focus
Teamleader Focus to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Teamleader Focus to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Teamleader Focus to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
Teamleader Focus to TypeformBuild and publish online forms, surveys, and quizzes with Typeform.
Teamleader Focus to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
Teamleader Focus to WixThe Wix website builder gives businesses of any size the tools to create, manage and grow a fully integrated...
More into Spike.sh
HubSpot to Spike.shHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Spike.shSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Spike.shSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Spike.shGoogle Sheets
Gmail to Spike.shGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Spike.shGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Teamleader Focus and Spike.sh, answered
What can start an automation from Teamleader Focus?
Any of Teamleader Focus's 5 triggers in the catalog, including New Company, New Contact, New Deal and Deal Accepted. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Spike.sh when something happens in Teamleader Focus?
Any of Spike.sh's 25 actions, including Create Incident, Update alert rule, Update escalation and Update on-call. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Spike.sh to Teamleader Focus?
Spike.sh has no triggers in the catalog today, so automations start in Teamleader Focus. If you need the other direction, ask: your agent reads Spike.sh's API documentation and adds it.
Do I have to build a connector for Teamleader Focus or Spike.sh?
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.