--- title: "Connect Pinpoint to Spike.sh - APIANT.ai" description: "When \"New Application\" fires in Pinpoint, your agent runs \"Add alert rule\" in Spike.sh." canonical: "https://apiant.ai/connect/pinpoint-to-spike-sh" --- # Connect Pinpoint to Spike.sh When **New Application** fires in [Pinpoint](https://apiant.ai/connections/pinpoint), your agent runs **Add alert rule** in [Spike.sh](https://apiant.ai/connections/spike-sh). Describe the whole flow and it is built, tested on every scenario and kept running. Pinpoint **4** triggers Pinpoint **17** actions Spike.sh **25** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Pinpoint and Spike.sh to do together? Give your AI client this address. `https://mcp.apiant.ai` One 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.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) Example flows ## What Pinpoint can start in Spike.sh - When **New Application** in Pinpoint then **Add alert rule** in Spike.sh - When **New Job** in Pinpoint then **Add escalation** 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 Pinpoint and Spike.sh ## Triggers and actions 4 triggers · 42 actions - Trigger **Application Stage Update** Triggers when an application moves to a different hiring stage in Pinpoint. - Trigger **New Application** Triggers when a new job application is submitted in Pinpoint. - Trigger **New Job** Triggers when a new job is created in Pinpoint, returning the job's details and custom field values. - Trigger **New Talent Pipeline Candidate** Triggers when a new candidate is added to your talent pipeline (job seekers) in Pinpoint. - Action **Add application** Creates a new application (candidate applying) for a job in Pinpoint. - Action **Add comment** Adds a comment to an application, candidate or job seeker in Pinpoint and returns the new comment. - Action **Add job** Creates a new job in Pinpoint with its title, description, compensation, application form settings and organisational links. - Action **Add requisition** Creates a requisition in Pinpoint from a requisition template and returns the new requisition. - Action **Get application** Returns a single application by its id, optionally with related records such as the candidate, job, stage and custom attributes. - Action **Get candidate** Returns a single Pinpoint candidate by ID, with optional related applications, job seekers, skills, HRIS references and custom attributes. - Action **Get job** Returns one job by its id, including its custom field values and any related records you ask for. - Action **List applications** Returns applications in your Pinpoint account, optionally filtered by job, candidate, stage, dates or other criteria. - Action **List candidates** Returns the candidates in your Pinpoint account, optionally narrowed by creation or update date, phone number, external reference or blocked status. - Action **List comments** Returns comments left on applications, candidates, jobs and other records in Pinpoint, optionally filtered by the record they belong to or by date. - Action **List interviews** Returns interviews scheduled in Pinpoint, optionally filtered by time, application or attendance. - Action **List job postings** Returns the job postings in your Pinpoint account, with optional filters for status, job, department, division, location, employment type, workplace type and dates. - Action **List jobs** Returns the jobs in your Pinpoint account, optionally filtered by status, department, location, dates and more. - Action **List requisitions** Returns the requisitions in your Pinpoint account, with optional filters by identifier and by created or updated date. - Action **List users** Returns the users in your Pinpoint account, optionally filtered by email, employee status or the jobs they manage, create or interview for. - Action **Update application** Updates an existing application's candidate details, address, hire date, start date or attached CV and cover letter. - Action **Update candidate** Updates an existing candidate's personal and contact details in Pinpoint. - Action **Acknowledge incident** Acknowledge one or more Spike.sh incidents by counter id or incident id. - Action **Add alert rule** Create a new alert routing/automation rule with conditions and actions. - Action **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. - Action **Add integration** Create a new integration for a team (source system that sends alerts into Spike). - Action **Add on-call** Create a new on-call schedule for a team. - Action **Add service** Create a new service in a team, with name and description. - Action **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. - Action **Delete alert rule** Archives (soft-deletes) a Spike alert rule so it no longer applies to incoming incidents. - Action **Delete escalation** Archives (soft-deletes) a Spike escalation policy by its ID. - Action **Escalate incident** Escalates one or more Spike incidents to the next step of their escalation policy. - Action **Get escalation** Get escalation policy details by id. - Action **Get incident** Fetch a single incident by counter id. - Action **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. - Action **Get service** Get a Spike service's details, along with its incidents and open-incident count. - Action **List alert rules** Lists all alert rules (enabled and disabled) configured for a Spike team. - Action **List escalations** Lists the escalation policies that belong to a Spike team. - Action **List incidents** Lists the incidents for a Spike.sh team. - Action **List on-calls** Lists the on-call schedules for a team. - Action **List services** Lists the services in a Spike team. - Action **List teams** Lists every team in your Spike organisation. Use a team's ID from here wherever other Spike actions ask for a team. - Action **Resolve incident** Resolve one or more incidents by counter id array. - Action **Update alert rule** Replace an existing Spike alert rule's name, conditions and actions. - Action **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. - Action **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. - Action **Update service** Updates the name and/or description of an existing Spike.sh service. ## Each app on its own - [ **Pinpoint** Pinpoint is talent acquisition software for in-house recruitment teams.](https://apiant.ai/connections/pinpoint) - [ **Spike.sh** Spike is an incident management system with unlimited alerts and on-call schedules](https://apiant.ai/connections/spike-sh) Reviews ## What our customers say ## More from Pinpoint - [ **Pinpoint to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/pinpoint-to-salesforce) - [ **Pinpoint to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/pinpoint-to-slack) - [ **Pinpoint to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/pinpoint-to-stripe) - [ **Pinpoint to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/pinpoint-to-shopify) - [ **Pinpoint to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/pinpoint-to-quickbooks-online) - [ **Pinpoint to Pipedrive** Pipedrive is a sales CRM and pipeline management tool.](https://apiant.ai/connect/pinpoint-to-pipedrive) ## More into Spike.sh - [ **HubSpot to Spike.sh** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-spike-sh) - [ **Salesforce to Spike.sh** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-spike-sh) - [ **Slack to Spike.sh** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-spike-sh) - [ **Google Sheets to Spike.sh** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-spike-sh) - [ **Gmail to Spike.sh** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-spike-sh) - [ **Google Calendar to Spike.sh** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-spike-sh) Questions ## Pinpoint and Spike.sh, answered ### ### What can start an automation from Pinpoint? Any of Pinpoint's 4 triggers in the catalog, including New Application, New Job, New Talent Pipeline Candidate and Application Stage Update. 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 Pinpoint? 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 Pinpoint? Spike.sh has no triggers in the catalog today, so automations start in Pinpoint. 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 Pinpoint 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 Pinpoint 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.