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

# Work.ink

1. Get your API key from the Work.ink dashboard's API settings.
2. Enter it in the project's Work.ink connection.
3. Add the Work.ink links you want users to complete.
4. Add a package, enable the provider, save, and test it from the flow page.

The current configuration requires manually supplied links. Some older editor copy mentions automatic link creation; use the links/readiness shown by the current saved configuration.

Vampauth prepares the per-session return destination through Work.ink's override integration. Users return through `/api/integrations/workink/callback`. You don't need a Linkvertise-style permanent target anchor.

## If it fails

* An explicit authentication rejection means replace the API key.
* A 429 from Work.ink means wait before trying again.
* A timeout or provider outage can interrupt a run even when saving the credential succeeded.
* A return in another browser session won't complete the original attempt.

Use the current Work.ink link and the return prepared for that session; don't save a temporary callback URL as the link users should always open.


---

# 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://vampauth.gitbook.io/vampauth-docs/integrations/checkpoint-providers/workink.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.