Integration
Connect ProProfs Project to Spike.sh
When Completed Subtask fires in ProProfs Project, your agent runs Add alert rule in Spike.sh. Describe the whole flow 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 ProProfs Project and Spike.sh to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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 ProProfs Project can start in Spike.sh
When Completed Subtask in ProProfs Project
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 ProProfs Project and Spike.sh
Triggers and actions 7 triggers · 32 actions
- Completed Subtask
Triggers when a subtask is marked complete in ProProfs Project.
- Completed Task
Triggers when a task is marked complete in ProProfs Project.
- New Client
Triggers when a new client is added in ProProfs Project.
- New Event
Triggers when a new event is created in ProProfs Project.
- New Project
Triggers when a new project is created in ProProfs Project.
- New Subtask
Triggers when a new subtask is created in ProProfs Project.
- New Task
Triggers when a new task is created in ProProfs Project.
- Create Client
Creates a new client in ProProfs Project with its contact details.
- Create Event
Creates a calendar event in ProProfs Project, optionally linked to a project.
- Create Project
Creates a new project in ProProfs Project, optionally with a client, dates, pricing and assigned users or teams.
- Create Subtask
Creates a subtask under an existing task in ProProfs Project.
- Create Task
Creates a new task in a ProProfs Project project.
- Get Subtask
Returns the details of a single subtask, including its parent task, project, dates, progress and assigned users.
- Get Task
Returns a single task by its id, including its project, dates, status and assigned users.
- 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 ProProfs Project
ProProfs Project to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
ProProfs Project to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
ProProfs Project to StripeStripe is a payment processing platform for online businesses.
ProProfs Project to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
ProProfs Project to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
ProProfs Project to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
More into Spike.sh
HubSpot to Spike.shHubSpot is your all-in-one stop for all of your marketing software needs.
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
ProProfs Project and Spike.sh, answered
What can start an automation from ProProfs Project?
Any of ProProfs Project's 7 triggers in the catalog, including Completed Subtask, Completed Task, New Client and New Event. 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 ProProfs Project?
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 ProProfs Project?
Spike.sh has no triggers in the catalog today, so automations start in ProProfs Project. 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 ProProfs Project 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.
Can my AI client use ProProfs Project and Spike.sh without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.