Integration
Connect Cliengo and GitHub
When Cliente Nuevo/Actualizado - New/Updated Customer fires in Cliengo, your agent runs Add Labels to Issue in GitHub, or New Branch in GitHub to Send message in Cliengo. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Cliengo and GitHub to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Cliengo and GitHub can do together
From Cliengo to GitHub
When Cliente Nuevo/Actualizado - New/Updated Customer in Cliengo
then Add Labels to Issue in GitHub
From GitHub to Cliengo
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Cliengo and GitHub
Triggers and actions 17 triggers · 38 actions
- Cliente Nuevo/Actualizado - New/Updated Customer
Triggers when a Cliengo contact (customer) is created or updated.
- Nuevo Cliente - New Customer
Triggers when a new contact (customer) is created in Cliengo.
- Actualizar Cliente / Update Customer
Updates an existing Cliengo contact's name, email, phone, status or assigned agent.
- Add conversation
Creates a new conversation in the Cliengo inbox on a given channel for a visitor.
- Assign conversation to operator
Assigns a conversation to an operator and returns the updated conversation.
- Buscar Agente / Search Agent
Finds agents (users/operators) in your Cliengo account whose name or email matches the text you enter.
- Buscar Contacto / Search Customer
Searches your Cliengo contacts by name, email, phone or other filters and returns the matching contacts.
- Close conversation
Closes a Cliengo inbox conversation, recording whether it resulted in a lead.
- Crear Cliente / Create Customer
Creates a new contact (customer) in Cliengo on the chosen channel.
- Delete contact
Deletes a contact from your Cliengo account.
- Get contact
Returns a single Cliengo contact (lead) by its id, including its status, rating, channel and campaign attribution.
- Get conversation
Returns a single inbox conversation by its ID, including channel, status, assignment, phase, tags and participants.
- List channels
Returns all active channels on the Cliengo account (websites, WhatsApp, Facebook, Instagram), each with its connection status and assigned chatbot.
- List conversation messages
Returns the messages of a Cliengo conversation in chronological order, optionally including system command events.
- List phases
Returns every phase (pipeline stage) of the conversation inbox, with its name and position.
- List tags
Returns every operator tag defined in the Cliengo account, with its name and color.
- List users
Returns the users (agents and operators) of your Cliengo company, with their name, email, role and active status.
- List WhatsApp templates
Returns the WhatsApp message templates (approved, pending and rejected) of a WhatsApp channel.
- Send message
Sends a message (text, image, command or note) into a Cliengo conversation on behalf of an operator, the chatbot or the visitor.
- Send WhatsApp template message
Sends an approved WhatsApp template message to one or more recipients through a WhatsApp Business channel.
- Update conversation phase
Moves a conversation to the chosen phase of your pipeline.
- Issue Closed
Triggers when an issue in a repository is closed.
- New Branch
Triggers when a new branch is created in a GitHub repository.
- New Collaborator
Triggers when a new collaborator is added to a GitHub repository.
- New Commit
Triggers when a new commit is pushed to a GitHub repository's default branch.
- New Commit Comment
Triggers when someone comments on a commit in a repository.
- New Gist
Triggers when you create a new gist on GitHub.
- New Global Event
Triggers when a new public event happens anywhere on GitHub, such as a push, fork, or new issue.
- New Issue
Triggers when a new issue is created in a repository.
- New Label
Triggers when a new label is added to a GitHub repository.
- New Milestone
Triggers when a new milestone is created in a repository.
- New Pull Request
Triggers when a new pull request is opened in a repository.
- New Release
Triggers when a new release is published in a GitHub repository.
- New Repo Event
Triggers when new activity (pushes, issues, pull requests, releases and more) happens in a GitHub repository.
- New Repository
Triggers when a new public repository appears under a GitHub user or organization.
- New Watcher
Triggers when someone starts watching a repository.
- Add Labels to Issue
Adds labels to an issue or pull request in a GitHub repository, keeping its existing labels.
- Check Organization Membership
Checks whether a GitHub user is a member of an organization and returns true or false.
- Create Branch
Creates a new branch in a repository, starting from the commit you choose.
- Create Comment
Adds a comment to an issue or pull request in a GitHub repository.
- Create Gist
Creates a new gist with one file on the connected GitHub account.
- Create Issue
Creates a new issue in a GitHub repository.
- Create or Update File
Creates a new file in a repository, or replaces an existing file's contents, as a commit.
- Create Pull Request
Opens a pull request asking to merge one branch into another.
- Delete Branch
Deletes a branch from a repository. Any open pull request from that branch is closed.
- Find Branch
Finds a branch in a GitHub repository by name and returns its latest commit and protection status.
- Find Issue
Finds an issue in a GitHub repository by its number and returns its title, body, state, author and labels.
- Find Organization
Finds a GitHub organization by its login and returns its profile details.
- Find Pull Request
Finds a pull request in a GitHub repository by its number and returns its title, state, branches and merge status.
- Find Repository
Returns a GitHub repository by its owner and name, including its description, visibility, default branch and counts.
- Find User
Finds a GitHub user by username and returns their public profile.
- Get File Contents
Returns a file from a GitHub repository, with its base64-encoded content, at the default branch or a chosen branch, tag or commit.
- Submit Review
Submits a review on a pull request: approve it, request changes, or leave a review comment.
- Update Issue
Updates an existing issue in a GitHub repository, such as its title, text, state, labels or assignees.
- Update Pull Request
Changes a pull request's title, description, target branch, or open/closed state.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Cliengo
Cliengo to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Cliengo to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Cliengo to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Cliengo to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Cliengo to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Cliengo to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into GitHub
ActiveCampaign to GitHubActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to GitHubOrganize anything with Airtable, a modern database created for everyone.
Asana to GitHubAsana is a collaborative information manager for workspace.
ClickUp to GitHubClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Discord to GitHubDiscord is an all-in-one voice and text chat for gamers.
Freshdesk to GitHubFreshdesk is a cloud-based customer support and helpdesk platform.
Questions
Cliengo and GitHub, answered
What can start an automation from Cliengo?
Any of Cliengo's 2 triggers in the catalog, including Cliente Nuevo/Actualizado - New/Updated Customer and Nuevo Cliente - New Customer. Describe the moment in plain language and your agent picks the right one.
What can your agent do in GitHub when something happens in Cliengo?
Any of GitHub's 19 actions, including Create Branch, Create Comment, Create Gist and Create Issue. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from GitHub to Cliengo?
Yes. When something happens in GitHub, your agent can act in Cliengo too. This page covers both directions: GitHub's triggers and Cliengo's actions are listed here as well.
Do I have to build a connector for Cliengo or GitHub?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Cliengo and GitHub without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.