Integration
Connect Moxie to Ashby
When Client Created fires in Moxie, your agent runs Create Candidate Note in Ashby. 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 Moxie and Ashby 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 Moxie can start in Ashby
When Client Created in Moxie
then Create Candidate Note in Ashby
When Client Updated in Moxie
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 Moxie and Ashby
Triggers and actions 30 triggers · 29 actions
Trigger
Agreement SentTriggers when a proposal is sent either via link or email.
Trigger
Agreement SignedTriggers when an agreement is accepted and signed with e-signature.
Trigger
Agreement ViewedTriggers when a user views the proposal.
Trigger
Client CreatedTriggers when a new client is created in Moxie.
Trigger
Client DeletedTriggers when a client record is deleted in Moxie.
Trigger
Client UpdatedTriggers when a client record is updated in Moxie.
Trigger
Form CompletedTriggers when a form is completed.
Trigger
Invoice SentTriggers when an invoice is sent in Moxie.
Trigger
Meeting CancelledTriggers when a meeting is cancelled
Trigger
Meeting ScheduledTriggers when a new meeting is scheduled
Trigger
Meeting UpdatedTriggers when a meeting is updated or rescheduled
Trigger
Opportunity CreatedTriggered with a pipeline opportunity is created
Trigger
Opportunity DeletedTriggered with a pipeline opportunity is deleted
Trigger
Opportunity UpdatedTriggered with a pipeline opportunity is updated
Trigger
Payment ReceivedTriggers when a payment is received either vial Stripe or manual entry.
Trigger
Project CompletedTriggers when a project is set to "complete" in Moxie.
Trigger
Project CreatedTriggers when a new project is created in Moxie.
Trigger
Project UpdatedTriggers when the settings for a project are updated.
Trigger
Task ApprovalTriggers when a new Deliverable is ready for client approval.
Trigger
Task CreatedTriggered when a Project Task is created
Trigger
Task DeletedTriggered when a Project Task is deleted
Trigger
Task UpdatedTriggered with a Project Task is updated.
Trigger
Ticket ClosedTriggers and a support ticket is closed
Trigger
Ticket CommentTriggers when a comment is created on a ticket
Trigger
Ticket CreatedTriggers when a new support ticket is created
Trigger
Ticket DeletedTriggers when a support ticket is deleted
Trigger
Ticket UpdatedTriggers when a support ticket is updated
Trigger
Time Worked CreatedTriggers when a new time worked entry is created.
Trigger
Time Worked DeletedTriggers when a time worked record is deleted.
Trigger
Time Worked UpdatedTriggers when a time worked entry has been updated.
Action
Create ClientCreates a new client record in Hectic
Action
Create ExpenseRecords a new expense in your Moxie accounting records, optionally filed under a vendor and allocated to a client.
Action
Create OpportunityCreate a new pipeline opportunity
Action
Create & Optionally Send InvoiceCreates an invoice for a client from the line items you supply, and emails it straight away when you fill in who to send it to. Left blank, the invoice is saved as a draft.
Action
Create or Update Calendar EventCreate or update a calendar event in Moxie
Action
Create ProjectCreate a project and optionally use a template
Action
Create TaskCreate a task in the project management system
Action
Create TicketCreate a Ticket for a client and contact
Action
Create Ticket CommentAdds a comment (public or private) to an existing ticket.
Action
Create Time WorkedCreates a time worked entry
Action
Delete Calendar EventDeletes a calendar event in Moxie by the external ID.
Action
Find a ClientFinds a client by either name or contact email address.
Action
Add candidate tagAdds an existing tag to a candidate in Ashby and returns the updated candidate.
Action
Add jobCreates 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 offerCreates 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 StageMoves 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 JobConsiders 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 CandidateCreates a new candidate in Ashby with their name, contact details, social profiles, location and source.
Action
Create Candidate NoteAdds a note to a candidate's profile in Ashby, optionally as HTML, private, or with notifications to subscribed users.
Action
Find CandidateReturns up to 100 candidates whose email address and/or name match the values you supply.
Action
Find JobReturns up to 100 jobs whose title or requisition ID matches the text you search for.
Action
Find Job ConsiderationReturns the applications (candidates being considered) for a job in Ashby, optionally narrowed by application status and creation date.
Action
Find OpeningReturns the openings whose identifier matches the one you supply, including each opening's state, jobs, locations, hiring team and custom fields.
Action
Get candidateReturns the full details of a single Ashby candidate, including contact info, tags, applications, files and custom field values.
Action
List departmentsReturns all departments and teams in your Ashby account, optionally including archived ones or only those changed since a previous sync.
Action
List locationsReturns the office and remote locations set up in your Ashby account, optionally including archived locations and regions.
Action
Update CandidateUpdates an existing candidate's name, contact details, social links, source, credited user and location in Ashby. Fields left blank are not changed.
Action
Update jobUpdates an existing job in Ashby — its title, team, location, default interview plan, employment type or requisition id.
Action
Update OpeningUpdates an existing opening in Ashby, such as its identifier, description, department, target dates, backfill flag or employment type. Returns the updated opening.
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 Moxie
Moxie to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Moxie to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Moxie to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Moxie to StripeStripe is a payment processing platform for online businesses.
Moxie to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Moxie to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Ashby
HubSpot to AshbyHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to AshbySalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to AshbySlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to AshbyGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to AshbyGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to AshbyGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Moxie and Ashby, answered
What can start an automation from Moxie?
Any of Moxie's 30 triggers in the catalog, including Client Created, Client Updated, Form Completed and Meeting Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Ashby when something happens in Moxie?
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 Moxie?
Ashby has no triggers in the catalog today, so automations start in Moxie. 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 Moxie 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 Moxie 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.