> For the complete documentation index, see [llms.txt](https://docs.spike.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spike.sh/integrations-guideline/create-integration-and-service-on-dashboard.md).

# Create integration and service on our dashboard

Integrations has to be added to a service. In this doc we will take you through the process of how to create a service and add any number of integrations to it.

## **What is a service?**

**You can think of services as a microservice.** Services are a way to scope your internal services from your architecture. Each of your services can have multiple integrations and you can create an unlimited number of services. We highly encourage you to create different services for each of your different modules.

[Learn more about services](https://docs.spike.sh/services/introduction-to-services-on-spike).

## Adding service

![](https://1743514643-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Ln3jS1bJTTsE3yoEcOu%2Fuploads%2Fgit-blob-19465a0fd708276bc23c67e4ec8e12b1c0e6263e%2Fimage.png?alt=media\&token=46a99c6b-38e9-4c29-812f-2d6ae9fd0877)

You can create a new service by clicking on the [New Service button](https://app.spike.sh/services/new) on the [services page](https://app.spike.sh/services).

Give it an appropriate name, **for ex: Billing service**. ( This way you can also integrate your payment gateway by adding another integration for every time payments fail ). Hit **Create service!**

***

Once the service is created you will be able to see an overview of your service with all of it's integrations.

### Adding integration

From the header, select Add integration. Optionally, on the sidebar select integrations and then add integration.

![Step 1 - Select an integration](https://1743514643-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Ln3jS1bJTTsE3yoEcOu%2Fuploads%2Fgit-blob-d5022c4749a8278cea3d90932609b5e9d73d66a1%2Fimage.png?alt=media\&token=3522ba4b-02bc-4338-b584-8808b4e52454)

![Step 2 - add service, escalation, Acknowledge timeout](https://1743514643-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Ln3jS1bJTTsE3yoEcOu%2Fuploads%2Fgit-blob-9324481cbba5049c1789d73f2c0d557e2b98e6ec%2Fimage.png?alt=media\&token=9d44f05a-14b5-48dd-948e-3d5596cc10d9)

[Acknowledge timeout](https://docs.spike.sh/incidents/acknowledge-timeout) and repeat escalations are optional but we highly recommend it.

![](https://1743514643-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Ln3jS1bJTTsE3yoEcOu%2Fuploads%2Fgit-blob-3b41d63fc41f4925e3f5ba5606a3afa8e661717c%2Fcopy-webhook.png?alt=media\&token=5af4449a-dd9c-47da-b2af-cb6dde5b9dc3)

The last bit on our dashboard is the final step of copying the webhook to be used on Pingdom used as an example here.

So, get the webhook by clicking on the **Copy Webhook** button.

![Final step - copy the integration webhook](https://1743514643-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Ln3jS1bJTTsE3yoEcOu%2Fuploads%2Fgit-blob-1091b64a5a54a22a316533f09ec8cb105aaceb6a%2Fintegration-last.png?alt=media\&token=60e1ff3d-cd7e-42d5-9499-b37b05822ba5)

{% hint style="danger" %}
Make sure to use the Pingdom webhook in Pingdom. Using it on other integrations might not give you the proper incident messages and will not reliably group repeated
{% endhint %}

{% hint style="success" %}
Not able to find an integration you are looking for?? Use the **Webhook** integration instead and paste it on any service.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.spike.sh/integrations-guideline/create-integration-and-service-on-dashboard.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.