Integration
Connect Openmic to Luma
When New Post-Call Summary fires in Openmic, your agent runs Add ticket type in Luma. 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 Openmic and Luma 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 Openmic can start in Luma
When New Post-Call Summary in Openmic
then Add ticket type in Luma
When New Post-Call Summary in Openmic
then Add event in Luma
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 Openmic and Luma
Triggers and actions 1 trigger · 56 actions
Trigger
New Post-Call SummaryTriggers when an Openmic call finishes, returning the completed call's numbers, agent, status and details.
Action
Add a ContactAdds a single contact to the list.
Action
Bulk Add ContactsAdds up to 1 000 contacts to the list in a single request.
Action
Create a CampaignCreates a new outbound dialing campaign. The campaign will begin dialing contacts within the `time_start`–`time_end` window on the specified `days`. If `timezone` is omitted the organization's default timezone is used.
Action
Create a Contact ListCreate a contact list
Action
Create an AgentCreates a new voice AI agent. > **Note:** `first_message` and `auto_first_message` are mutually exclusive. Providing both returns a `400` error.
Action
Create a Phone CallInitiates a new outbound phone call from a number registered in your organization. **Rate limit:** 5 requests per minute.
Action
Create a Tool for an AgentAdds a new tool to the agent's toolset. When `type` is `api_request`, the `url` field is **required**.
Action
Delete a CampaignDelete a campaign
Action
Delete a Contact ListDelete a contact list
Action
Delete an AgentPermanently deletes an agent. Returns `409 Conflict` if the agent is currently linked to a phone number or campaign.
Action
Delete a ToolPermanently removes a tool from the agent.
Action
Delete Contacts from a ListBulk-deletes contacts by their IDs. Accepts up to 1 000 IDs per request.
Action
Find BotReturns the full details of a single agent.
Action
Find CallReturns details and current status of a single call by its CUID.
Action
Get a CampaignGet a campaign
Action
Get a Contact ListGet a contact list
Action
Get an SMS LogReturns a single SMS log entry enriched with message details fetched live from the SMS provider: message body, delivery status, sent/delivered timestamps, and failure reason. If provider details are unavailable, the entry is returned with `status: "u
Action
Get a Phone NumberReturns details for a single phone number including linked agents.
Action
Get a ToolReturns details for a single tool.
Action
Get a VoiceReturns details for a single voice by its numeric ID.
Action
Get CallsReturns a cursor-paginated list of calls, newest first.
Action
Get UsageReturns call-minutes and sent-SMS usage for your organization, grouped by day, week, or month (UTC buckets; weekly buckets start on Monday). When from_date is omitted, the range defaults to the last 30 days for day, 12 weeks for week, and 12 months f
Action
Link an Agent to a Phone NumberAssociates an agent with a phone number for the given `direction`. | Direction | Effect | |-----------|--------| | `inbound` | Agent handles incoming calls on this number | | `outbound` | Agent is used as the default for outbound calls from this num
Action
List CampaignsReturns a cursor-paginated list of campaigns, newest first.
Action
List Contact ListsList contact lists
Action
List Contacts in a ListList contacts in a list
Action
List Phone NumbersReturns a cursor-paginated list of phone numbers in your organization.
Action
List SMS LogsReturns a cursor-paginated list of SMS log entries for your organization, newest first. Entries contain delivery metadata (direction, phone numbers, timestamps) — message bodies are not stored.
Action
List Tools for an AgentReturns a cursor-paginated list of tools attached to the agent.
Action
List VoicesReturns a cursor-paginated catalogue of available voices. Use the `voice` field from a voice record when creating or updating an agent.
Action
Send SMSSend an SMS message to a phone number. Messages are queued for delivery.
Action
Unlink an Agent from a Phone NumberRemoves the agent association from a phone number for the given direction.
Action
Update a CampaignPartially updates a campaign. Only the fields you include are modified.
Action
Update a ContactPartially updates a single contact.
Action
Update a Contact ListUpdate a contact list
Action
Update an AgentPartially updates an agent. Only the fields you include are modified. Set `knowledge_base_id` to `null` to detach the current knowledge base.
Action
Update a ToolPartially updates a tool. Only the fields you include are modified.
Action
Add eventAdds an existing event to your Luma calendar — either a Luma event you manage or an event hosted on another platform. The event is approved right away unless you choose to keep it pending for admin review.
Action
Add guestsAdds one or more guests to a Luma event, optionally assigning ticket types, an approval status, and whether Luma emails them. Returns any guests Luma skipped.
Action
Add hostAdds a host to a Luma event, as a manager or as check-in staff, by email address.
Action
Add ticket typeCreates a new ticket type (free or paid) for a Luma event. Paid ticket types require the calendar to have a connected Stripe account.
Action
Apply contact tagApplies a contact tag to existing contacts on your Luma calendar, identified by user ID or email. Does not create new contacts.
Action
Block contactBlocks a contact on your Luma calendar so they can't follow it or join its events, and stop receiving your invites and newsletters.
Action
Cancel eventCancels a Luma event. The event is permanently deleted, all guests are notified, and paid guests can optionally be refunded.
Action
Create Calendar PersonAdds a person to your Luma calendar as a contact by email, optionally with a name and contact tags, so you can invite them to events and send newsletters.
Action
Get calendarReturns the details of the Luma calendar your connected API key belongs to, including its name, URL, location, social handles and default event settings.
Action
Get eventReturns the details of a Luma event, including its schedule, location, visibility, hosts and, for events you manage, guest counts by status.
Action
Get guestReturns one guest of a Luma event, looked up by guest ID, ticket key, guest key or email, including their approval status, registration answers and tickets.
Action
Import contactsImports contacts into your Luma calendar so you can invite them to events and send them newsletters, optionally tagging them.
Action
List contactsReturns the contacts (people) on your Luma calendar, optionally filtered by a name/email search, tags or membership status.
Action
List eventsReturns the events on your Luma calendar, optionally filtered by date range, submission status, platform and access level.
Action
List guestsReturns the guests who have registered for or been invited to a Luma event, with their approval status, contact details, registration answers and tickets.
Action
List ticket typesReturns every ticket type set up for a Luma event, including its name, price and capacity.
Action
Send invitesSends people an email invite (and an SMS if their phone is linked to Luma) to a Luma event. Returns any invitees who were skipped because they unsubscribed, were removed, or are blocked.
Action
Update eventUpdates an existing Luma event's details, such as its name, time, location, description, capacity, registration settings and page appearance. Fields left blank keep their current values.
Action
Update guest statusChanges a guest's registration status for a Luma event — approve (Going), decline, move back to pending approval, or waitlist — optionally refunding a paid guest and adding a personal note to the notification email.
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 Openmic
Openmic to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Openmic to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Openmic to StripeStripe is a payment processing platform for online businesses.
Openmic to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Openmic to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Openmic to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Luma
HubSpot to LumaHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to LumaSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to LumaSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to LumaGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to LumaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LumaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Openmic and Luma, answered
What can start an automation from Openmic?
Any of Openmic's 1 trigger in the catalog, including New Post-Call Summary. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Luma when something happens in Openmic?
Any of Luma's 19 actions, including Create Calendar Person, Send invites, Update event and Update guest status. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Luma to Openmic?
Luma has no triggers in the catalog today, so automations start in Openmic. If you need the other direction, ask: your agent reads Luma's API documentation and adds it.
Do I have to build a connector for Openmic or Luma?
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 Openmic and Luma 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.