Integration
Connect Noko to Livestorm
When Entry Changed fires in Noko, your agent runs Create Event in Livestorm. 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 Noko and Livestorm 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 Noko can start in Livestorm
When Entry Changed in Noko
then Create Event in Livestorm
When Invoice Changed in Noko
then Update Event in Livestorm
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 Noko and Livestorm
Triggers and actions 6 triggers · 30 actions
Trigger
Entry ChangedTriggers when a Noko time entry is created or changed.
Trigger
Invoice ChangedTriggers when a Noko invoice is created or changed.
Trigger
New EntryTriggers when a new time entry is logged in Noko.
Trigger
New ExpenseTriggers when a new expense is logged in Noko.
Trigger
New InvoiceTriggers when a new invoice is created in Noko.
Trigger
New ProjectTriggers when a new project is created in Noko.
Action
Approve EntryMarks a Noko time entry as approved.
Action
Archive ProjectArchives a Noko project.
Action
Create EntryLogs a new time entry in Noko.
Action
Create ExpenseLogs a new expense against a Noko project.
Action
Create ProjectCreates a new Noko project.
Action
Create TagsCreates one or more Noko tags.
Action
Delete EntryDeletes a Noko time entry.
Action
Find ExpenseFinds the most recent Noko expense matching the filters.
Action
Find InvoiceFinds a Noko invoice by reference, state or company.
Action
Find ProjectFinds a Noko project by name.
Action
Find UserFinds a Noko user by name or email.
Action
Get EntryReturns a single Noko time entry by its ID.
Action
Mark Invoice as PaidMarks a Noko invoice as paid.
Action
Update EntryUpdates a Noko time entry's date, minutes, description, project or user.
Action
Create EventCreates a new Livestorm event with its first session, either from scratch or by duplicating the settings of an existing event.
Action
Create RegistrantRegisters a person for an upcoming Livestorm event session, with their email, name, registration fields and UTM tracking data.
Action
Create SessionSchedules a new session for an existing Livestorm event. Returns the created session, including its room link, status and scheduled start time.
Action
Find PeopleFinds people in your Livestorm workspace by email address, optionally limited to participants or team members.
Action
Find SessionFinds event sessions in your Livestorm workspace whose name matches the one you give, optionally narrowed by status and date range. Returns the matching sessions and the first match.
Action
Get eventReturns a single Livestorm event, including its title, status, registration link, settings, owner and registration fields.
Action
Get personReturns the details of a person in your Livestorm workspace, such as their name, email, role and timezone.
Action
Get sessionReturns a single Livestorm session, including its status, schedule, room link and attendee counts, optionally with its event, people, chat messages, questions or recordings.
Action
List eventsReturns the events in your Livestorm workspace, optionally filtered by title, scheduling status, tag, or creation and update dates.
Action
List session questionsReturns all the questions attendees asked during a Livestorm session, with any answers given.
Action
List sessionsReturns the sessions across all events in your Livestorm workspace, optionally filtered by status, scheduled start date, creation date or last update date.
Action
Remove EventDeletes a single Livestorm event.
Action
Remove RegistrantRemoves a registrant from a Livestorm event session, cancelling their registration.
Action
Remove SessionDeletes a single Livestorm event session.
Action
Update EventUpdates an existing Livestorm event, changing only the details you fill in, such as its title, description, status or room settings.
Action
Update SessionUpdates a Livestorm session's name, start date/time or timezone. Fields left blank keep their current values.
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 Noko
Noko to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Noko to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Noko to StripeStripe is a payment processing platform for online businesses.
Noko to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Noko to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Noko to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Livestorm
HubSpot to LivestormHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to LivestormSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to LivestormSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to LivestormGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to LivestormGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LivestormGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Noko and Livestorm, answered
What can start an automation from Noko?
Any of Noko's 6 triggers in the catalog, including Entry Changed, Invoice Changed, New Entry and New Expense. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Livestorm when something happens in Noko?
Any of Livestorm's 16 actions, including Create Event, Create Registrant, Create Session and Update Event. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Livestorm to Noko?
Livestorm has no triggers in the catalog today, so automations start in Noko. If you need the other direction, ask: your agent reads Livestorm's API documentation and adds it.
Do I have to build a connector for Noko or Livestorm?
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 Noko and Livestorm 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.