Open Office Hours
Open Office Hours Season 1: Session 15 - Rapidi MCP Server
Last week we looked at Albert, the AI assistant that lives inside MyRapidi. This week we walked through the next layer: the Rapidi MCP Server. It is the bridge that lets external AI tools like Claude reach the same context Albert has, so you can troubleshoot, configure, and run your integrations from whichever AI tool you already use.
→
Open Office Hours Season 1: Session 14 - Albert AI Agent
Last week we introduced AI in MyRapidi at a high level. This week we go one layer deeper into Albert, the AI assistant that lives inside the platform. Albert is not a bolt-on chatbot. He has direct access to your service, your documentation, and your transfer history, and he is built to help you actually get work done, from troubleshooting an error to creating a new connection or pulling a list of transfers in a specific status.
→
Open Office Hours Season 1: Session 13 - AI in MyRapidi: An Overview
Integration platforms used to be about pipes and plumbing. You connected systems, mapped fields, scheduled syncs, and watched logs. AI is changing that. The question is no longer just "how do I move this data?" but "what should the platform do for me automatically?"
→
Open Office Hours Season 1: Session 12 - Tags & Reusability
You have three subsidiaries running the same ERP. Each one needs the same Salesforce integration - same fields, same logic, same schedule. Do you really need three separate sets of transfers?
→
Open Office Hours Season 1: Session 11 - Triggers and Near-Real-Time Patterns
Your ERP has just updated a price list. Your sales team is quoting from Salesforce. How fast does that change need to reach them - and what happens if the sync fires at the wrong moment?
→
Open Office Hours Season 1: Session 10 - Scheduling: Automate Your Sync the Smart Way
When you have data flowing between two systems, getting the timing right is just as important as getting the data mapping right. In Rapidi, scheduling controls when and how your transfers run — including how often, in what order, and what happens when runs overlap.
→
Open Office Hours Season 1: Session 9 - Link Storage Deep Dive
When you sync records between two systems, there has to be something that remembers which record in the source matches which record in the destination. In Rapidi, that something is called a Link Storage. It stores the primary key pairs between your systems so that transfers know whether to create a new record or update an existing one.
→
Open Office Hours Season 1: Session 8 - Logs & Runs: Your Troubleshooting Toolkit
When your integration throws an error, the first question is always the same: where do I look? In MyRapidi, logs and runs give you that answer. They show exactly what happened, which transfer caused it, how long it took, and what the error message says. Once you know how to read them, troubleshooting becomes a lot faster.
→
Open Office Hours Season 1: Session 6 - Timestamps & RTI
When Rapidi runs a transfer, it doesn't pull all your data every time. It only pulls what changed since the last run. That keeps your source systems from getting hammered with unnecessary queries. But how does it actually know what changed? The answer is two things working together: source control fields and the RTI.
→
What Are Open Office Hours? Season 1: Session 2 - Rapidi Transfer Design 101
On January 15, 2026, we launched our Open Office Hours series. These live training sessions run from January through April and cover everything from basic setup to advanced configuration. All Rapidi customers can join live or watch the recordings.
→
What are Open Office Hours? Season 1: Session 1 – MyRapidi Walkthrough
Starting January 15, 2026, we're launching 12 free weekly training sessions designed to help you get more confident and capable with your Rapidi integration.
→
Introducting Open Office Hours Season 1: 14 Weeks of Free Integration Training
Starting January 15, 2026, we're launching 14 free weekly training sessions designed to help you get more confident and capable with your Rapidi integration.
→