> For the complete documentation index, see [llms.txt](https://docs.fairmarkit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fairmarkit.com/buyers/integrations/servicenow-spo-integration/quick-start-servicenow-spo-integration.md).
# Quick start: ServiceNow SPO integration
### 1. Open a sourcing request
In ServiceNow SPO, you will need to create a sourcing request for goods or services line items and submit your request.
### 2. Fairmarkit auto-creates & submits an event
If the request matches you organization's requirements for automated sourcing, Fairmarkit automatically creates and event. Using AI technology and the event details, Fairmarkit recommends and invites the best suppliers for your event and submits it. When suppliers respond to your event, Fairmarkit instantaneously sends their responses to you in ServiceNow SPO. You will also receive a response if a supplier sends a no bid response.
### 3. Review and award a response
In ServiceNow SPO, review and award your preferred response. Once awarded, ServiceNow SPO automatically creates a purchase requisition and submits it to the approval chain to become a purchase order. After awarding, Fairmarkit notifies the winning supplier to look for a purchase order.
---
# 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.fairmarkit.com/buyers/integrations/servicenow-spo-integration/quick-start-servicenow-spo-integration.md?ask=&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.
