---
title: "Connect GitHub and WeTravel - APIANT.ai"
description: "When \"New Branch\" fires in GitHub, your agent runs \"Get order\" in WeTravel, or \"Lead Updated\" in WeTravel to \"Add Labels to Issue\" in GitHub."
canonical: "https://apiant.ai/connect/github-to-wetravel"
---

# Connect GitHub and WeTravel

When **New Branch** fires in [GitHub](https://apiant.ai/connections/github), your agent runs **Get order** in [WeTravel](https://apiant.ai/connections/wetravel), or **Lead Updated** in WeTravel to **Add Labels to Issue** in GitHub. Describe the whole flow and it is built, tested on every scenario and kept running.

GitHub **15** triggers GitHub **19** actions WeTravel **3** triggers WeTravel **10** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want GitHub and WeTravel to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One 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.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

Example flows

## What GitHub and WeTravel can do together

### From GitHub to WeTravel

- When **New Branch** in GitHub then **Get order** in WeTravel
- When **New Collaborator** in GitHub then **List leads** in WeTravel

### From WeTravel to GitHub

- When **Lead Updated** in WeTravel then **Add Labels to Issue** in GitHub
- When **New Lead** in WeTravel then **Create Issue** in GitHub

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 GitHub and WeTravel

## Triggers and actions 18 triggers · 29 actions

- Trigger

**Issue Closed**

Triggers when an issue in a repository is closed.

- Trigger

**New Branch**

Triggers when a new branch is created in a GitHub repository.

- Trigger

**New Collaborator**

Triggers when a new collaborator is added to a GitHub repository.

- Trigger

**New Commit**

Triggers when a new commit is pushed to a GitHub repository's default branch.

- Trigger

**New Commit Comment**

Triggers when someone comments on a commit in a repository.

- Trigger

**New Gist**

Triggers when you create a new gist on GitHub.

- Trigger

**New Global Event**

Triggers when a new public event happens anywhere on GitHub, such as a push, fork, or new issue.

- Trigger

**New Issue**

Triggers when a new issue is created in a repository.

- Trigger

**New Label**

Triggers when a new label is added to a GitHub repository.

- Trigger

**New Milestone**

Triggers when a new milestone is created in a repository.

- Trigger

**New Pull Request**

Triggers when a new pull request is opened in a repository.

- Trigger

**New Release**

Triggers when a new release is published in a GitHub repository.

- Trigger

**New Repo Event**

Triggers when new activity (pushes, issues, pull requests, releases and more) happens in a GitHub repository.

- Trigger

**New Repository**

Triggers when a new public repository appears under a GitHub user or organization.

- Trigger

**New Watcher**

Triggers when someone starts watching a repository.

- Action

**Add Labels to Issue**

Adds labels to an issue or pull request in a GitHub repository, keeping its existing labels.

- Action

**Check Organization Membership**

Checks whether a GitHub user is a member of an organization and returns true or false.

- Action

**Create Branch**

Creates a new branch in a repository, starting from the commit you choose.

- Action

**Create Comment**

Adds a comment to an issue or pull request in a GitHub repository.

- Action

**Create Gist**

Creates a new gist with one file on the connected GitHub account.

- Action

**Create Issue**

Creates a new issue in a GitHub repository.

- Action

**Create or Update File**

Creates a new file in a repository, or replaces an existing file's contents, as a commit.

- Action

**Create Pull Request**

Opens a pull request asking to merge one branch into another.

- Action

**Delete Branch**

Deletes a branch from a repository. Any open pull request from that branch is closed.

- Action

**Find Branch**

Finds a branch in a GitHub repository by name and returns its latest commit and protection status.

- Action

**Find Issue**

Finds an issue in a GitHub repository by its number and returns its title, body, state, author and labels.

- Action

**Find Organization**

Finds a GitHub organization by its login and returns its profile details.

- Action

**Find Pull Request**

Finds a pull request in a GitHub repository by its number and returns its title, state, branches and merge status.

- Action

**Find Repository**

Returns a GitHub repository by its owner and name, including its description, visibility, default branch and counts.

- Action

**Find User**

Finds a GitHub user by username and returns their public profile.

- Action

**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.

- Action

**Submit Review**

Submits a review on a pull request: approve it, request changes, or leave a review comment.

- Action

**Update Issue**

Updates an existing issue in a GitHub repository, such as its title, text, state, labels or assignees.

- Action

**Update Pull Request**

Changes a pull request's title, description, target branch, or open/closed state.

- Trigger

**Lead Updated**

Triggers when a WeTravel lead is created or updated (for example, when the person requests again or books).

- Trigger

**New Lead**

Triggers when a new lead is captured for one of your WeTravel trips.

- Trigger

**Transaction Updated**

Triggers when a WeTravel transaction is created or updated, such as a payment, refund or payout changing status.

- Action

**Add payment link**

Creates a WeTravel payment link for a trip with its dates, currency, fee handling and price, optionally with a deposit and installment payment plan.

- Action

**Add trip**

Creates a draft trip in WeTravel, which can then be built out and published.

- Action

**Get order**

Returns a single trip order (booking), including amounts paid and due, packages and add-ons, participants and installments.

- Action

**Get payment link**

Returns a WeTravel payment link by its UUID, including its trip and pricing details.

- Action

**List leads**

Returns the leads (trip inquiries) in your WeTravel account, optionally filtered by trip, booking status, lead type and request date.

- Action

**List orders**

Returns the orders (bookings) placed on a trip, with amounts paid and due, buyer and booked packages.

- Action

**List transactions**

Returns the transactions (payments and refunds) on your WeTravel account, optionally filtered.

- Action

**List trips**

Returns all trips in your WeTravel account, with their titles, destinations, dates and listing status.

- Action

**Publish trip**

Publishes a draft trip so its booking page goes live on WeTravel, and returns the published trip.

- Action

**Update trip**

Updates an existing draft trip's details, such as title, dates, group size, pricing currency and booking settings. Only the fields you fill in are changed.

## Each app on its own

- [ **GitHub** GitHub is the perfect place to share code and work collaboratively on private and open source software.](https://apiant.ai/connections/github)
- [ **WeTravel** WeTravel is an all-in-one operating system for multi-day travel businesses—build itineraries, manage...](https://apiant.ai/connections/wetravel)

Reviews

## What our customers say

## More from GitHub

- [ **GitHub to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/github-to-hubspot)
- [ **GitHub to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/github-to-salesforce)
- [ **GitHub to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/github-to-slack)
- [ **GitHub to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/github-to-google-sheets)
- [ **GitHub to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/github-to-gmail)
- [ **GitHub to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/github-to-google-calendar)

## More into WeTravel

- [ **HubSpot to WeTravel** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-wetravel)
- [ **Salesforce to WeTravel** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-wetravel)
- [ **Slack to WeTravel** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-wetravel)
- [ **Google Sheets to WeTravel** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-wetravel)
- [ **Gmail to WeTravel** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-wetravel)
- [ **Google Calendar to WeTravel** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-wetravel)

Questions

## GitHub and WeTravel, answered

###

### What can start an automation from GitHub?

Any of GitHub's 15 triggers in the catalog, including New Branch, New Collaborator, New Commit and New Commit Comment. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in WeTravel when something happens in GitHub?

Any of WeTravel's 10 actions, including Update trip, Add payment link, Add trip and Get order. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from WeTravel to GitHub?

Yes. When something happens in WeTravel, your agent can act in GitHub too. This page covers both directions: WeTravel's triggers and GitHub's actions are listed here as well.

###

### Do I have to build a connector for GitHub or WeTravel?

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 GitHub and WeTravel 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.
