[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Start a Habitica party quest on a schedule

> Force-start a pending Habitica party quest at the time you choose and report who has not answered. From Claude Code, n8n or a script, nothing to host.

Source: https://cotlet.dev/integrations/habitica-api-mcp-server/start-party-quest-on-schedule

You sent a quest invite on Monday. By Friday two members have not answered and the quest sits pending while the boss waits.

Cotlet does it in your own Habitica account with get\_party and start\_quest, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=habitica) [All Habitica tools](https://cotlet.dev/integrations/habitica-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Habitica do this on its own?

Habitica starts a quest when every member has answered or when the owner or leader begins it by hand (checked 17 Oct 2026). There is no timer. The API has a force-start call, and the wiki shows a calendar plus Zapier webhook setup that calls it. That route needs your token and a setup per party.

## How you do it in Habitica today

1. You use a quest scroll, which sends the invite to all party members.
2. You open your party page and read the member list, where each member shows as accepted, rejected or pending.
3. You wait until everyone has responded, because a quest begins on its own once all members have answered.
4. If they do not, you, as quest owner or party leader, begin the quest by hand before the others respond.
5. The waiting is manual: nothing starts the quest at a time you pick.

## How to start a Habitica party quest on a schedule

Prompt

```
Check my Habitica party quest. If it is still pending and some members have not answered, force-start it at 18:00 on Friday and tell me who was left out.
```

1. 01  
### Read the party  
get\_party returns the quest state and each member's answer. If no quest is pending, the agent reports that and stops.
2. 02  
### Check your role  
Only the quest owner or the party leader can begin a quest early. If your account is neither, the agent says so and does not call anything.
3. 03  
### Wait for the hour  
The job runs at the time you set, for example Friday 18:00, and reads the party again just before acting.
4. 04  
### Start the quest  
start\_quest force-starts the quest with the answers it has. It affects every member, so it asks for your OK on each call until you switch that off.
5. 05  
### Report who was left out  
The agent names the members who had not accepted, so you can tell them.

### What you get back

Example data

```
Quest pending since Monday.
Accepted 3, pending 2.
Force-started at 18:00.
Not in the quest: Mira and Tomek (no answer).
```

### Other ways to ask

- Do not start anything, just tell me on Thursday who has not answered the quest invite.
- Start the quest as soon as 4 of 5 members have accepted.
- Every Monday, tell me whether a quest is active and how it is going.

## What Habitica allows, and what to know first

- A quest is started with a quest scroll, which sends an invite to all party members.
- A party can take part in only one quest at a time.
- Only the quest owner or the party leader can begin, cancel or abort a quest.
- A pending quest shows each member as accepted, rejected or pending.
- Everyone who takes part gets the same reward when the quest ends.

start\_quest asks for your OK by default. To run it on a schedule without you, switch confirmation off for that tool in your dashboard.

Sources: [Habitica Wiki: Quests](https://habitica.fandom.com/wiki/Quests) · [Habitica Wiki: The Keep: Scheduling Quest Starts with Zapier and API](https://habitica.fandom.com/wiki/The%5FKeep:Scheduling%5FQuest%5FStarts%5Fwith%5FZapier%5Fand%5FAPI) · [Habitica API documentation](https://habitica.com/apidoc/)

## Call start\_quest from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/habitica/quest/start \
  -H "Authorization: Bearer $COTLET_API_KEY"
```

Example response

```
{
"quest": "The Dilatory Distraction",
"state": "active",
"members_in": 3,
"members_out": [
"Mira",
"Tomek"
]
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is habitica\_write → start\_quest. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/habitica-api-mcp-server.md#automations)

## Habitica tools this automation uses

__Cotlet Habitica tools used to start a Habitica party quest on a schedule__
| Tool | Parameters |
| ------------ | ---------- |
| get\_party | none |
| start\_quest | none |

[All 14 Habitica tools with descriptions](https://cotlet.dev/integrations/habitica-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Habitica to Cotlet?

Yes. You sign in to Habitica yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Habitica once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More Habitica automations

- [Create Habitica dailies from a list](https://cotlet.dev/integrations/habitica-api-mcp-server/create-recurring-tasks-from-a-list.md)
- [Check off done Habitica dailies from your notes](https://cotlet.dev/integrations/habitica-api-mcp-server/check-off-done-dailies.md)
- [Habitica API and MCP server: every tool](https://cotlet.dev/integrations/habitica-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Habitica.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Habitica.

[Sign up free](https://cotlet.dev/app/signup?app=habitica)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.