Integration
Connect DocuWriter.ai to Wachete
When something happens in DocuWriter.ai, your agent does the next thing in Wachete. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want DocuWriter.ai and Wachete to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with DocuWriter.ai and Wachete
Triggers and actions 3 triggers · 16 actions
Trigger
New GenerationTriggers when new generation is created.
- Add document
Create a new document within a Space. POST /api/spaces/{space}/documents (Bearer token auth).
- Add space
Create a new Space to organize documentation. POST /api/spaces (Bearer token auth).
- Delete document
Delete a document within a Space. DELETE /api/spaces/{space}/documents/{spaceMenuItem} (Bearer token auth).
- Find documents by keyword
Search for documents within a Space by keyword. POST /api/spaces/{space}/search (Bearer token auth).
- Get document
Retrieve a document within a Space by id. GET /api/spaces/{space}/documents/{spaceMenuItem} (Bearer token auth).
- Get generation
Retrieve a single documentation generation by id, including its status and result. GET /api/generations/{id} (Bearer token auth).
- List generations
List the user's documentation generations. GET /api/generations (Bearer token auth).
- List spaces
List the user's Spaces (collaborative documentation collections). GET /api/spaces (Bearer token auth).
- Update document
Update an existing document within a Space. PUT /api/spaces/{space}/documents/{spaceMenuItem} (Bearer token auth).
Trigger
Any new notificationFires when there is a new change notification from any monitor in your Wachete account.
- New notification for monitor
Fires when there is a new change notification from the specified Wachete monitor (taskId).
- Create monitor
Create a new Wachete monitor (wachet) that watches a web page or part of a page for changes.
- Delete monitor
Delete a Wachete monitor by its ID.
- Get monitor
Get information about a specific Wachete monitor by its ID.
- Get monitor data
Get the captured data/history for a Wachete monitor, optionally as a diff and within a date range.
- List folders
List folder contents, optionally under a parent folder.
- List notifications
List change notifications, optionally filtered by monitor (taskId) and date range.
- Update monitor
Change the settings of an existing Wachete monitor — name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value — including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.