Integrations
What Railen connects to, and what it does not
Every row below is a technical connection that exists in the product today. Systems Railen runs alongside, but does not connect to, are listed separately so the two are never confused.
Last checked against the product on September 24, 2026
Connected
| System | What it is | How Railen connects | Direction | What moves |
|---|---|---|---|---|
| Your CRM | Lead management | ADF/XML lead, or email to your inbox | Railen to CRM | Lead, contact, vehicle and the conversation |
| Your inventory feed | Vehicle data | Feed ingest | Feed to Railen | Vehicles, prices, photos and availability |
| XTime | Service scheduling | API | Both ways | Service openings and appointments |
| DealerFX | Service scheduling | API | Both ways | Service openings and appointments |
| Your website | Where the agent runs | One script tag, added by your website provider | None | Nothing on your site is replaced |
Runs alongside, not connected
| System | What that means |
|---|---|
| CDK | No connection. Railen does not read from or write to the DMS. |
| Reynolds and Reynolds | No connection. Railen does not read from or write to the DMS. |
| Dealer.com | No connection. The agent runs on a Dealer.com site through the script tag. |
| eDealer | No connection. The agent runs on an eDealer site through the script tag. |
"Works alongside" on this site means exactly this: Railen runs next to these systems, and nothing about them has to change.
Partnerships and certification
Nothing on this page claims a partnership or a certification. Where Railen connects to a system, it is a technical connection. If certification matters for your store, ask us about the specific system.