> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/integrations/integration-reference/abc-ignite/check-in-alerts.md).

# Check-in alerts

Perkville's integration with ABC Ignite can automatically post a check-in alert to a member's account based on activity in Perkville, such as an alert to thank the member for referring a friend or completing a challenge.

The Perkville team will need to know the following to configure an alert:

* Alert title (22 character max)
* Alert note (255 character max)
* Color: Red, Blue, Green, Yellow, Orange, or Purple
* Whether or not to show the alert once

{% hint style="warning" %}
We recommend only showing the alert once. If the trigger for the alert is a recurring event, alerts can start to pile up on a member's account.
{% endhint %}

* Alert sound
  * Account
  * Birthday
  * Enjoy Your Workout Male Voice
  * Have a Wonderful Workout
  * Please Sign Contract
  * Thanks
  * Alliance Member
  * Check Status
  * Enrollment Unsuccessful
  * Member Needs Photo
  * Rescan Your Card
  * Upgrade
  * Bell 1
  * Congratulations
  * Expired
  * Nice Workout
  * Restricted Access
  * Welcome
  * Bell 2
  * Contract Expires Soon
  * Frozen
  * PT Orientation
  * Terminate
  * Welcome Male Voice
  * Bell 3
  * Enjoy Your Workout
  * Has Message
  * Please See Manager
  * Thank You
  * Your Membership Expires Soon


---

# 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.perkville.com/integrations/integration-reference/abc-ignite/check-in-alerts.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.
