--- title: "Connect folk to Spike.sh - APIANT.ai" description: "When \"Company Added\" fires in folk, your agent runs \"Add alert rule\" in Spike.sh." canonical: "https://apiant.ai/connect/folk-to-spike-sh" --- # Connect folk to Spike.sh When **Company Added** fires in [folk](https://apiant.ai/connections/folk), 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. folk **11** triggers folk **16** 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 folk 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 folk can start in Spike.sh - When **Company Added** in folk then **Add alert rule** in Spike.sh - When **Company Custom Field Updated** in folk 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 folk and Spike.sh ## Triggers and actions 11 triggers · 41 actions - Trigger **Company Added** Triggers when a new company is created or added to a group. - Trigger **Company Custom Field Updated** Triggers when a company custom field (for example tag, status, text, assignee) is updated. - Trigger **Company Removed** Triggers when a company is deleted from the workspace or removed from a group. - Trigger **Company Updated** Triggers when a company basic field (like name, email or URL) in a group is updated. - Trigger **Deal Added** Fires when a new deal is created. - Trigger **Deal Removed** Fires when a deal is deleted from a pipeline. - Trigger **Deal Updated** Fires when a deal is updated (stage change, field update). - Trigger **Person Added** Triggers when a new person is created or added to a group. - Trigger **Person Custom Field Updated** Triggers when a person custom field (for example tag, status, text, assignee) is updated. - Trigger **Person Removed** Triggers when a person is deleted from the workspace or removed from a group. - Trigger **Person Updated** Triggers when a person basic field (like first name, job title, email or URL) in a group is updated. - Action **Create Company** Creates a company in folk, optionally adding it to a group and setting that group's custom fields. - Action **Create Deal** Creates a deal in a folk group, optionally linked to companies and people, and sets that deal type's custom fields. - Action **Create Group** Creates a group in folk. A default "All people" table view is added to the group automatically. - Action **Create Note** Creates a note on a folk person, company or deal. Optionally posts it as a reply to an existing note. - Action **Create Person** Creates a person in folk, optionally adding them to a group and setting that group's custom fields. - Action **Create Reminder** Creates a reminder on a folk person, company or deal, scheduled with an iCalendar recurrence rule. - Action **Delete Company** Deletes a company from folk by its id. - Action **Delete Person** Deletes a person from folk by their id. This also removes their custom fields, notes and associations. - Action **Find a Company** Searches folk companies by name, email or website and returns the matches, with the first one broken out for easy mapping. - Action **Find a Person** Searches folk people by email, full name or phone and returns the matches, with the first one broken out for easy mapping. - Action **Get a Company** Fetches one folk company by id, including its custom field values. - Action **Get a Note** Fetches one folk note by id, with its text, author and the record it is attached to. - Action **Get a Person** Fetches one folk person by id, including their custom field values. - Action **List Groups** Returns the groups in the folk workspace, with each group's id, name and visibility. - Action **Update Company** Updates a folk company. Only the fields you fill in are changed; list fields such as emails replace the whole list. - Action **Update Person** Updates a folk person. Only the fields you fill in are changed; list fields such as emails replace the whole list. - 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 - [ **folk** folk is the next generation CRM for teams](https://apiant.ai/connections/folk) - [ **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 folk - [ **folk to Ascora** Ascora is a complete Job Mangement System for trades and services-based businesses](https://apiant.ai/connect/folk-to-ascora) - [ **folk to OpenRouter** OpenRouter is a unified interface to AI models.](https://apiant.ai/connect/folk-to-openrouter) - [ **folk to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/folk-to-hubspot) - [ **folk to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/folk-to-salesforce) - [ **folk to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/folk-to-slack) - [ **folk to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/folk-to-google-sheets) ## 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 ## folk and Spike.sh, answered ### ### What can start an automation from folk? Any of folk's 11 triggers in the catalog, including Company Added, Company Custom Field Updated, Company Removed and Company Updated. 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 folk? 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 folk? Spike.sh has no triggers in the catalog today, so automations start in folk. 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 folk 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 folk 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.