🔌 Make Integration

Make (formerly Integromat) is a no-code automation platform. You can connect Perfect Wiki to Make today in two ways:

• HTTP module + Perfect Wiki Public API. Best for regular scenarios that create, update or read pages on a trigger, for example "when a new employee is added in the HR system, create their onboarding page."
• MCP Client app + Perfect Wiki MCP server. Best when you want AI to choose the right action, or when you want to call Perfect Wiki tools without building each request yourself.

Option 1: HTTP module and the Public API

Step 1. Get an API token

1. Open the Perfect Wiki administration panel.
2. Find the knowledgebase you want Make to work with.
3. Open the API Access section and click Generate API Key.
4. Copy the token right away. It is shown only once.

Each token works with one knowledgebase. Full details are in 🔌 Perfect Wiki Public API.

Step 2. Add the HTTP "Make a request" module

1. In your scenario, add HTTP → Make a request.
2. Set Authentication type to API key, then next to Credentials click Add to create a keychain:
   • Key: Bearer YOUR_API_TOKEN (include the word Bearer and a space)
   • API key placement: In the header
   • API key parameter name: Authorization
3. Fill in URL and Method from the table below.
4. For POST requests, set Body content type to application/json, Body input method to JSON string, and paste the JSON into Body content.
5. Turn on Parse response so later modules can use fields such as the new page ID.

Page content must be HTML, not Markdown.

Example: create an onboarding page for a new hire

Put the HTTP module after your trigger (for example a webhook or an HR app module) and map the fields from it. In Make, values from module 1 look like {{1.firstName}}:

{
  "title": "Welcome, {{1.firstName}} {{1.lastName}}",
  "content": "<p>Start date: {{1.startDate}}</p><p>Manager: {{1.manager}}</p>",
  "tags": ["onboarding"],
  "parentId": "ONBOARDING_PARENT_PAGE_ID"
}

The response contains the new page ID in page.id. Use it to update the same page later, or post its link to Jira, Teams or email.

Example: answer a question from your knowledgebase

POST https://api.perfectwiki.xyz/api/public-api/v1/knowledgebase/query

{ "q": "{{1.question}}" }

The answer is in aiBotResponse.response, and links to the source pages are in aiBotResponse.relatedPages. Each call counts as an AI request on your plan.

Option 2: MCP Client app and the MCP server

1. In your scenario, add an MCP Client module and click Create a connection.
2. In the MCP Server field, click + New MCP Server.
3. In URL, enter https://api.perfectwiki.xyz/mcp.
4. Click Save. A Perfect Wiki sign-in window opens: choose the knowledgebases and the access level (Read only or Read & Write), and approve.
5. Pick a module:
   • Call a tool runs one specific Perfect Wiki tool, for example ask or create_page. This is the most predictable option and the best one for testing.
   • Execute an action with AI lets AI choose and run the right tools based on a task you describe, for example "Find our travel policy and summarize the per-diem rules."

Available tools: ask, list_knowledgebases, get_knowledgebase, list_pages, get_page, create_page, update_page and delete_page. Read more in 🔌 Perfect Wiki MCP Server.

Tip: to test the connection, use Call a tool with list_knowledgebases. It should return the knowledgebases you selected when signing in.

FAQ

Is there a dedicated Perfect Wiki app in Make?

Not yet. The HTTP module and the MCP Client app give you full access to Perfect Wiki today. If you'd like a dedicated app, let us know at docs.perfectwiki.com/feedback.

Can a scenario start when a page is created or changed?

Perfect Wiki doesn't send webhooks yet. To react to changes, schedule a scenario that lists pages on a regular interval and compares the results.

Are there rate limits?

Yes: 10 requests per second and 60 per minute for each token. If a scenario processes many bundles at once, add a Sleep module or lower the number of bundles processed per run. A 429 error means you hit the limit; wait and retry.

I'm getting a 401 error.

Check that the keychain Key starts with Bearer followed by a space, and that the token hasn't been regenerated since you copied it.

I'm getting a 402 error.

If the code is TRIAL_EXPIRED, your free trial has ended and API access is paused until your organization picks a paid plan. If you only get 402 from the AI query endpoint, you've used this month's AI query allowance; the other endpoints keep working.

Which other automation tools work with Perfect Wiki?

Zapier, Power Automate, n8n, Pipedream and Activepieces.

Need help?

If something doesn't work as expected, contact support.