Integration
Connect Jenkins and Record360
When New build fires in Jenkins, your agent runs Create Task in Record360, or Inspection Created in Record360 to Add job by copying in Jenkins. 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 Jenkins and Record360 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Jenkins and Record360 can do together
From Jenkins to Record360
When New build in Jenkins
then Create Task in Record360
When New Job in Jenkins
then Update Task in Record360
From Record360 to Jenkins
When Inspection Created in Record360
then Add job by copying in Jenkins
When Task Completed in Record360
then Build Job in Jenkins
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 Jenkins and Record360
Triggers and actions 5 triggers · 34 actions
Trigger
New buildTriggers when a new build of the chosen Jenkins job starts.
Trigger
New JobTriggers when a new job is added to your Jenkins server.
Trigger
New Job Status NotificationTriggers when a job starts a new build.
Action
Add job by copyingCreates a new Jenkins job by copying the configuration of an existing job.
Action
Build JobStarts a new build of a job, optionally with build parameters. The build is queued and the queue item's location is returned.
Action
Delete JobPermanently deletes a job and its build history.
Action
Delete queue itemRemoves a waiting item from a pipeline's build queue so it never runs.
Action
Disable JobDisables a job so it no longer builds.
Action
Enable JobEnables a disabled job so it can be built again.
Action
Get JobReturns a job's details, including its builds, health and last build results.
Action
Get Last BuildReturns the most recent build of a job, with its number, result, duration and whether it is still running.
Action
List buildsReturns every build of a Jenkins job, newest first, with each build's number, result and timing.
Action
List JobsReturns the jobs on your Jenkins server with each job's name, URL and status color.
Action
List NodesReturns the build agents (nodes) on the Jenkins server with whether each is online and idle.
Action
List Queue ItemsReturns the builds waiting in the Jenkins build queue.
Action
Stop Last BuildAborts the most recent build of a job if it is still running.
Trigger
Inspection CreatedTriggers when a new inspection is completed in Record360.
Trigger
Task CompletedTriggers when a task is completed in Record360.
Action
Create or Update Unit by Reference NumberUpdates the unit with this reference number, or creates it when none exists.
Action
Create TaskCreates a task, such as an inspection to run on a unit, assigned to a user, a location or a user group.
Action
Create UnitCreates a unit (a vehicle or piece of equipment) in Record360. Fails if a unit with that reference number already exists.
Action
Delete TaskDeletes a task.
Action
Get InspectionReturns one inspection, with links to its dashboard page and PDF.
Action
Get Inspection Share LinkReturns a temporary shareable link to an inspection and when it expires.
Action
Get TaskReturns one task by its ID.
Action
Get UnitReturns one unit by its Record360 unit ID.
Action
Get Unit by Reference NumberReturns one unit by its reference number.
Action
List InspectionsReturns a page of inspections, optionally filtered by type and creation date.
Action
List Inspections for UnitReturns a page of inspections of one unit, found by its reference number.
Action
List LocationsReturns a page of the account's locations.
Action
List TasksReturns a page of tasks, optionally filtered by status and dates.
Action
List UnitsReturns a page of units, optionally filtered by reference number or serial number.
Action
List User GroupsReturns a page of the account's user groups.
Action
List UsersReturns a page of the account's users.
Action
List WorkflowsReturns a page of the account's inspection workflows.
Action
Update TaskUpdates a task. Only the fields you fill in change.
Action
Update UnitUpdates the details of a unit, found by its Record360 unit ID. Only the fields you fill in change.
Action
Update Unit by Reference NumberUpdates the details of a unit found by its reference number. Only the fields you fill in change.
Action
Update UserUpdates a user's first name, last name or external ID.
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 Jenkins
Jenkins to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Jenkins to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Jenkins to MailchimpMailchimp marketing automation and email platform.
Jenkins to StripeStripe is a payment processing platform for online businesses.
Jenkins to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Jenkins to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Record360
HubSpot to Record360HubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to Record360Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Record360Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Record360Google Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to Record360Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to Record360Mailchimp marketing automation and email platform.
Questions
Jenkins and Record360, answered
What can start an automation from Jenkins?
Any of Jenkins's 3 triggers in the catalog, including New build, New Job and New Job Status Notification. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Record360 when something happens in Jenkins?
Any of Record360's 21 actions, including Create or Update Unit by Reference Number, Create Task, Create Unit and Update Task. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Record360 to Jenkins?
Yes. When something happens in Record360, your agent can act in Jenkins too. This page covers both directions: Record360's triggers and Jenkins's actions are listed here as well.
Do I have to build a connector for Jenkins or Record360?
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 Jenkins and Record360 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.