> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/product-guides-and-integrations/integrations/front.md).

# Front

Connect Luciq to Front so users report bugs in-app. Pick the inbox that receives them and choose which report details get forwarded.

Integrating Luciq with Front allows your users to send feedback, ask questions, and report bugs in-app without the need to open another app to send it.

{% stepper %}
{% step %}
**Enter your token**

Enter your token. If you don't have one, click on *here* right below the token field and you'll be redirected to Front so you can generate one.
{% endstep %}

{% step %}
**Choose the Inbox name**

Choose the *Inbox name*. You can also choose which details get forwarded as well.
{% endstep %}

{% step %}
**Test the integration**

At this point, we just need to test your integration so that we're sure everything is working smoothly.
{% endstep %}

{% step %}
**Finish setup**

All done! Your integration is now set up and ready to go. From this final page, you can allow automatic forwarding (don't worry though, this can be reconfigured at any time!)
{% endstep %}

{% step %}
**Example forwarded issue**

Issues forwarded to Front should look something like this.
{% endstep %}
{% endstepper %}


---

# 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.luciq.ai/product-guides-and-integrations/integrations/front.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.