+
Connect Algolia to GitHub
Automate Algolia and GitHub with AI
Documentation in GitHub repos is hard to search until it lives in Algolia indexes your product actually queries. Your Operator agent on OpenClaw watches merged markdown in GitHub, pushes updated pages to the Algolia index you name, and can remove stale records when files delete. Tell it to reindex a folder after a release and it reads the repo tree and refreshes Algolia without a manual deploy step.
It reaches both apps directly or through connectors like Composio MCP and Pipedream MCP, which handle the sign in and token refresh, so there is no Zap to build and no API keys to paste.
What your agent can do with Algolia and GitHub
What your agent does in Algolia
Add AB Test
Tool to create an A/B test comparing search performance between two index variants. Use when you need to test different search configurations, ranking strategies, or index settings and measure their impact on user behavior.
Add or Replace Record
Tool to add or replace a specific record in an index by objectID. If a record with the given objectID exists, it is replaced; otherwise, a new record is created. Use when you need to upsert an object with a known ID.
Add Record to Index
Tool to add a record to an index with auto-generated objectID. Records with matching IDs are replaced. Use when you need to insert a new object into an index.
Browse Algolia Index
Tool to retrieve all records from an index. Use when you need to export or iterate through an entire index dataset.
Clear Objects
Tool to clear records of an index without affecting settings. Use when you need to completely wipe all objects (e.g., after a bulk reindex) while preserving index configuration.
Clear Rules
Tool to delete all rules in an index. Use when you need to wipe all rules before re-creating them. Use after confirming no critical rules require retention.
What your agent does in GitHub
Abort Repository Migration
Tool to abort a repository migration that is queued or in progress. Use when you need to cancel an ongoing migration operation.
Accept a repository invitation
Accepts a PENDING repository invitation that has been issued to the authenticated user.
Add app access restrictions
Adds GitHub Apps to the list of apps allowed to push to a protected branch. The branch must already have protection rules with restrictions enabled. This endpoint only works for organization repositories, not personal repositories. Apps...
Add a repository collaborator
Adds a GitHub user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation ma...
Add assignees to an issue
Adds assignees to a GitHub issue. This action only adds users - it does not remove existing assignees. Changes are silently ignored if the authenticated user lacks push access to the repository.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's GitHub account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the...
How it works
Tell the agent what you want to happen between Algolia and GitHub, for example to watch one and act in the other, or to keep the two in step. It reads what it needs from Algolia, works out what to do, and runs the matching action in GitHub without you mapping a single field.
You can have it run once, on a schedule, or whenever something changes. Ask it for a status any time and it reads the latest from both apps back to you in the same chat.
Common questions about Algolia and GitHub
- How do I connect Algolia and GitHub to Operator?
- You authorize Algolia and GitHub once each from your Operator dashboard. Operator holds both connections and refreshes the access tokens for you, so your agent keeps working across them without you signing in again.
- What can my agent do across Algolia and GitHub?
- You describe the outcome in plain language and your agent works between the two, reading from one and acting in the other. It picks the right Algolia and GitHub actions on its own, so you do not map fields or pick triggers.
- Can my agent keep Algolia and GitHub in sync?
- Yes. It can watch Algolia and act in GitHub, or keep both in step, reading from one and running the matching update in the other. This runs on demand when you ask or on a schedule you set.
- Do I need to build a workflow or write code?
- No. There is no workflow to build, no fields to map, and no API keys to paste. Operator manages both connections, and you give the agent instructions in plain language.
Algolia and GitHub integrations
Put your agent on Algolia and GitHub
Sign in, connect both apps, and hand your agent the work. The same setup reaches every app in the catalog. Your first week is free.
Try for free