> For the complete documentation index, see [llms.txt](https://showreward.gitbook.io/showreward-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://showreward.gitbook.io/showreward-docs/gohighlevel/calendar-links.md).

# Link calendars and open the reward portal after booking

A calendar link tells ShowReward which campaign and call type a GoHighLevel booking belongs to. For example, a Triage calendar can create Triage appointments, while a Closing calendar creates Closing appointments.

The calendar-linking, redirect and test-booking chapters are covered in [Tutorial 03: Create a Campaign and Test a Booking](/showreward-docs/campaigns.md#tutorial-03).

## Link a calendar

1. Connect GoHighLevel in **Settings → Calendar integrations**.
2. Create and save your campaign. Calendar links become available after the campaign exists.
3. Reopen the campaign and go to **Calls**.
4. Give each active call type a name, such as Triage or Closing.
5. In **GoHighLevel calendars**, choose the matching calendar for each call type. Select **Not linked** for a type that should not receive bookings from a GoHighLevel calendar.
6. Choose whether to enable **Redirect to reward after booking** for each linked calendar.
7. If you added, renamed, or activated a call type, use the campaign's **Save** button to save the type and apply pending calendar changes. For calendar mapping changes to already-saved call types, you can use **Save and apply in GoHighLevel**.
8. Check the confirmation and any warnings. **Unapplied changes** or **Pending application** means the selection has not yet been applied.

Create calendars in GoHighLevel first if the list is empty. Each call type can have one calendar. A calendar already reserved by another campaign or call type cannot be assigned again; use a separate calendar or update its existing link.

## Use the booking redirect

With **Redirect to reward after booking** enabled, ShowReward updates the GoHighLevel calendar's confirmation page to open the participant's reward portal after booking. This changes that calendar's post-booking behavior, so test the booking journey before sending traffic.

When applied successfully, the calendar row displays **Redirect active in GHL**. With the switch off, the calendar can remain linked for appointment synchronization while the automatic portal redirect is disabled.

If ShowReward warns that it could not update the confirmation page, review the GoHighLevel connection and retry. Do not assume that a saved campaign means the redirect was applied successfully.

## Test the full journey

1. Open the public GoHighLevel booking page for the linked calendar.
2. Book a test appointment with an email you control.
3. Confirm that ShowReward receives the appointment under the right campaign and call type.
4. If the redirect is enabled, confirm that the browser opens that test participant's portal.
5. Check the appointment time and the campaign's tasks in the portal.

Treat participant portal links as private links. Share each participant's link only with that participant.


---

# 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://showreward.gitbook.io/showreward-docs/gohighlevel/calendar-links.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.