---
title: "Connect inMobile - SMS gateway to Ashby - APIANT.ai"
description: "When \"New email event\" fires in inMobile - SMS gateway, your agent runs \"Create Candidate Note\" in Ashby."
canonical: "https://apiant.ai/connect/inmobile-sms-gateway-to-ashby"
---

# Connect inMobile - SMS gateway to Ashby

When **New email event** fires in [inMobile - SMS gateway](https://apiant.ai/connections/inmobile-sms-gateway), your agent runs **Create Candidate Note** in [Ashby](https://apiant.ai/connections/ashby). Describe the whole flow and it is built, tested on every scenario and kept running.

inMobile - SMS gateway **4** triggers inMobile - SMS gateway **15** actions Ashby **17** actions

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

## What do you want inMobile - SMS gateway and Ashby 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 inMobile - SMS gateway can start in Ashby

- When **New email event** in inMobile - SMS gateway then **Create Candidate Note** in Ashby
- When **New incoming RCS message** in inMobile - SMS gateway then **Add candidate tag** in Ashby

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 inMobile - SMS gateway and Ashby

## Triggers and actions 4 triggers · 32 actions

- Trigger

**New email event**

Triggers when a new email event occurs on a message you sent, such as delivered, opened, clicked, bounced or unsubscribed.

- Trigger

**New incoming RCS message**

Triggers when a new RCS message is received by one of your inMobile RCS agents, including text, file, location and suggestion responses.

- Trigger

**New incoming SMS message**

Triggers when a new SMS message is received on one of your inMobile numbers.

- Trigger

**New SMS status report**

Triggers when a delivery status report arrives for a sent SMS message. inMobile hands out each report only once, so a report collected by this trigger can't be retrieved again through the API.

- Action

**Add list**

Creates a new recipient list in your inMobile account and returns its id, name and creation time.

- Action

**Add Mobile Number to Blacklist**

Adds a mobile number to the inMobile blacklist so it no longer receives messages, and returns the created blacklist entry.

- Action

**Add recipient**

Creates a recipient with a phone number and optional contact details on an inMobile SMS list, and returns the new recipient.

- Action

**Cancel SMS message**

Cancels scheduled SMS messages that have not been sent yet and returns a result for each message.

- Action

**Create or Update Contact**

Creates a recipient on an inMobile list, or updates the existing recipient on that list with the same phone number.

- Action

**Delete Contact**

Deletes a contact (recipient) from an inMobile list.

- Action

**Find recipient by number**

Returns the recipient on an inMobile list that has the specified phone number, and reports whether one was found.

- Action

**List lists**

Returns all recipient lists in the inMobile account, with each list's id, name and creation time.

- Action

**List recipients**

Returns all recipients in an inMobile list, including their phone numbers and fields.

- Action

**Parse phone numbers**

Checks a list of phone numbers and returns, for each one, whether it is valid along with its cleaned number, country code and local number.

- Action

**Remove Mobile Number From Blacklist**

Removes a mobile number from your inMobile blacklist, so it can receive messages again.

- Action

**Send email**

Sends an email with a subject and HTML body to up to 100 recipients through inMobile, optionally scheduled for later, and returns the message id and accepted recipients.

- Action

**Send RCS text message**

Sends a text-only RCS message from one of your RCS agents to a mobile number, with optional suggested replies and actions. Returns the message id and the parsed recipient number.

- Action

**Send SMS Message**

Sends one SMS text message to a mobile number, immediately or at a scheduled time, and returns the message ID and how many SMS parts it uses.

- Action

**Update recipient**

Updates an existing recipient on an inMobile list. Only the details you fill in are changed; anything left blank keeps its current value.

- Action

**Add candidate tag**

Adds an existing tag to a candidate in Ashby and returns the updated candidate.

- Action

**Add job**

Creates a new job in Ashby with a title, department/team and location, optionally applying a job template, interview plan, employment type and brand.

- Action

**Add offer**

Creates an offer for a candidate's application in Ashby by submitting the offer form for an offer process that has already been started.

- Action

**Change Job Consideration Stage**

Moves a candidate's application (their consideration for a job) to a different interview stage, optionally with an archive reason and rejection email when archiving.

- Action

**Consider Candidate for Job**

Considers a candidate for a job in Ashby by creating a new application, optionally placing it in a specific interview plan and stage with a source and credited user.

- Action

**Create Candidate**

Creates a new candidate in Ashby with their name, contact details, social profiles, location and source.

- Action

**Create Candidate Note**

Adds a note to a candidate's profile in Ashby, optionally as HTML, private, or with notifications to subscribed users.

- Action

**Find Candidate**

Returns up to 100 candidates whose email address and/or name match the values you supply.

- Action

**Find Job**

Returns up to 100 jobs whose title or requisition ID matches the text you search for.

- Action

**Find Job Consideration**

Returns the applications (candidates being considered) for a job in Ashby, optionally narrowed by application status and creation date.

- Action

**Find Opening**

Returns the openings whose identifier matches the one you supply, including each opening's state, jobs, locations, hiring team and custom fields.

- Action

**Get candidate**

Returns the full details of a single Ashby candidate, including contact info, tags, applications, files and custom field values.

- Action

**List departments**

Returns all departments and teams in your Ashby account, optionally including archived ones or only those changed since a previous sync.

- Action

**List locations**

Returns the office and remote locations set up in your Ashby account, optionally including archived locations and regions.

- Action

**Update Candidate**

Updates an existing candidate's name, contact details, social links, source, credited user and location in Ashby. Fields left blank are not changed.

- Action

**Update job**

Updates an existing job in Ashby — its title, team, location, default interview plan, employment type or requisition id.

- Action

**Update Opening**

Updates an existing opening in Ashby, such as its identifier, description, department, target dates, backfill flag or employment type. Returns the updated opening.

## Each app on its own

- [ **inMobile - SMS gateway** inMobile is a powerful SMS gateway. inMobile makes it easy for you to send personalized SMS messages, manage...](https://apiant.ai/connections/inmobile-sms-gateway)
- [ **Ashby** Ashby's all-in-one recruiting software consolidates your ATS, Analytics, Scheduling, and CRM.](https://apiant.ai/connections/ashby)

Reviews

## What our customers say

## More from inMobile - SMS gateway

- [ **inMobile - SMS gateway to Mailercloud** Mailercloud is a cloud-based email marketing platform that allows businesses to launch email marketing...](https://apiant.ai/connect/inmobile-sms-gateway-to-mailercloud)
- [ **inMobile - SMS gateway to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/inmobile-sms-gateway-to-salesforce)
- [ **inMobile - SMS gateway to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/inmobile-sms-gateway-to-slack)
- [ **inMobile - SMS gateway to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/inmobile-sms-gateway-to-mailchimp)
- [ **inMobile - SMS gateway to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/inmobile-sms-gateway-to-stripe)
- [ **inMobile - SMS gateway to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/inmobile-sms-gateway-to-shopify)

## More into Ashby

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

Questions

## inMobile - SMS gateway and Ashby, answered

###

### What can start an automation from inMobile - SMS gateway?

Any of inMobile - SMS gateway's 4 triggers in the catalog, including New email event, New incoming RCS message, New incoming SMS message and New SMS status report. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Ashby when something happens in inMobile - SMS gateway?

Any of Ashby's 17 actions, including Create Candidate, Create Candidate Note, Update Candidate and Update job. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Ashby to inMobile - SMS gateway?

Ashby has no triggers in the catalog today, so automations start in inMobile - SMS gateway. If you need the other direction, ask: your agent reads Ashby's API documentation and adds it.

###

### Do I have to build a connector for inMobile - SMS gateway or Ashby?

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 inMobile - SMS gateway and Ashby 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.
