Integration
Connect The Old Reader to Luma
When New item fires in The Old Reader, 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 The Old Reader 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)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 The Old Reader can start in Luma
When New item in The Old Reader
then Add ticket type 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 The Old Reader and Luma
Triggers and actions 1 trigger · 29 actions
- New item
Triggers when a new item arrives in your reading list, a folder or a subscription.
- Add subscription
Subscribes the account to a feed or website by its URL and returns the new subscription's stream id.
- Delete folder
Deletes a folder in The Old Reader and moves its subscriptions to the default folder.
- Delete subscription
Unsubscribes from a feed in The Old Reader.
- Get items
Returns the full contents (title, body, author, feed, read/starred state) of one or more items by their ids.
- Get unread counts
Returns unread item counts for the whole reading list and for each folder, subscription and friend.
- List folders
Returns the list of folders in your The Old Reader account.
- List items
Returns the items (articles) in a stream such as your reading list, starred items, a folder or a subscription.
- List subscriptions
Returns every feed subscription in your The Old Reader account, with each feed's title, folders, site URL and icon.
- Mark all items as read
Marks all items in a stream (everything, a folder, a subscription or a friend's shares) as read, optionally only those older than a given time.
- Update folder
Renames a folder in The Old Reader.
- Update item
Updates an item's state: marks it read or unread, starred, liked or shared.
- Update subscription
Renames a subscription or moves it between folders.
- Add guests
Adds 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.
- Add host
Adds a host to a Luma event, as a manager or as check-in staff, by email address.
- Add ticket type
Creates a new ticket type (free or paid) for a Luma event. Paid ticket types require the calendar to have a connected Stripe account.
- Apply contact tag
Applies a contact tag to existing contacts on your Luma calendar, identified by user ID or email. Does not create new contacts.
- Block contact
Blocks a contact on your Luma calendar so they can't follow it or join its events, and stop receiving your invites and newsletters.
- Cancel event
Cancels a Luma event. The event is permanently deleted, all guests are notified, and paid guests can optionally be refunded.
- Create Calendar Person
Adds 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.
- Get calendar
Returns the details of the Luma calendar your connected API key belongs to, including its name, URL, location, social handles and default event settings.
- Get event
Returns the details of a Luma event, including its schedule, location, visibility, hosts and, for events you manage, guest counts by status.
- Get guest
Returns 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.
- Import contacts
Imports contacts into your Luma calendar so you can invite them to events and send them newsletters, optionally tagging them.
- List contacts
Returns the contacts (people) on your Luma calendar, optionally filtered by a name/email search, tags or membership status.
- List events
Returns the events on your Luma calendar, optionally filtered by date range, submission status, platform and access level.
- List guests
Returns the guests who have registered for or been invited to a Luma event, with their approval status, contact details, registration answers and tickets.
- List ticket types
Returns every ticket type set up for a Luma event, including its name, price and capacity.
- Send invites
Sends 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.
- Update guest status
Changes 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 The Old Reader
The Old Reader to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
The Old Reader to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
The Old Reader to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
The Old Reader to TypeformBuild and publish online forms, surveys, and quizzes with Typeform.
The Old Reader to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
The Old Reader to WixThe Wix website builder gives businesses of any size the tools to create, manage and grow a fully integrated...
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
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
The Old Reader and Luma, answered
What can start an automation from The Old Reader?
Any of The Old Reader's 1 trigger in the catalog, including New item. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Luma when something happens in The Old Reader?
Any of Luma's 17 actions, including Create Calendar Person, Send invites, Update guest status and Add guests. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Luma to The Old Reader?
Luma has no triggers in the catalog today, so automations start in The Old Reader. 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 The Old Reader 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 The Old Reader 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.