> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/integrations/overview/heroku-integration.md).
# Heroku Integration
Heroku is a platform-as-a-service (PaaS) that enables teams to build, run, and scale applications in the cloud.
Integrating Heroku with Sprinto allows you to:
* Automate infrastructure monitoring controls
* Sync application and add-on data
* Continuously monitor access and configuration posture
* Maintain up-to-date compliance evidence
This integration uses OAuth and requires admin access to your Heroku account.
***
### Prerequisites
Before connecting Heroku to Sprinto, ensure that:
* You have **Admin access** to the Heroku account.
* You are authorised to approve third-party OAuth integrations.
* You understand that Sprinto requests **read-only access** to apps and resources.
***
### Permissions and Data Access
#### Permissions required
Sprinto requests the following OAuth scopes:
* `identity`
* `read`
This provides read-only access to apps and resources, excluding account-level information.
#### Data used by Sprinto
Sprinto may access the following metadata:
* Name
* Account ID
* Regions
* Account
* Add-ons
* Apps
* heroku-postgres
* heroku-redis
Sprinto does not modify your Heroku infrastructure.
***
### How to Connect Heroku
#### Step 1: Navigate to Integrations
1. Log in to your Sprinto dashboard.
2. Go to **Settings** from the left navigation panel.
3. Click **Integrations**.
4. Under the **All** tab, search for **Heroku**.
5. Click **Connect** next to Heroku.
***
#### Step 2: Review Permissions
A **Connect Heroku** drawer appears.
Review:
* Automated controls and checks
* Required permissions
* Data accessed by Sprinto
* Access type (Admin access required)
Click **Next** to proceed.
***
#### Step 3: Authorise the Connection
In the **Setup Heroku Integration** screen:
1. Confirm the connection type is **OAuth**.
2. Review the prerequisites and requested scopes.
3. Click **Connect Heroku**.
You will be redirected to the Heroku login page.
***
#### Step 4: Authenticate with Heroku
1. Enter your Heroku email and password.
2. Review the requested access.
3. Approve the integration.
After successful authentication, you will be redirected back to Sprinto.
***
### Post-Connection Flow
Once connected:
* The integration status changes to **Active**.
* Sprinto begins syncing Heroku account and application metadata.
* Automated monitoring controls and checks start running.
* Initial sync may take up to **24 hours** to reflect across dashboards.
You can monitor integration health under:
* **Settings → Integrations**
* Relevant controls under **Monitoring**
***
### Troubleshooting
#### Unable to authenticate
* Ensure you are using a Heroku account with **Admin access**.
* Confirm that third-party integrations are permitted.
#### Redirect loop or login failure
* Clear browser cache and retry.
* Use an incognito/private window.
#### Data not reflecting in Sprinto
* Allow up to 24 hours for the initial sync.
* Verify that the integration status is **Active**.
* Disconnect and reconnect the integration if required.
***
If you have any questions or concerns during the integration process, don't hesitate to reach out to Sprinto Support via the in-app chat or write to us at . We're here to help!
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.sprinto.com/integrations/overview/heroku-integration.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.