How can I connect a legacy database to a visual workflow with native connectors?

[Sofia35]

I’ve been using a visual workflow builder for my team’s internal processes, but I’m hitting a wall trying to connect it to our legacy database without writing custom scripts. Has anyone managed to bridge that gap using only the platform’s native connectors and maybe a bit of API wizardry?

[Scott47]

Yep, we tried this last quarter. The platform had a native database connector that talked to the legacy system's API layer, so we didn’t write scripts. It needed careful field mapping, and we saw about a minute latency in testing, but it ran in the background after that.

[Gregory43]

Auth with the old DB was rough, but the wizard helped, and we ended up a small wrapper service to translate credentials. It kept us from coding, which was the main win.

[Noah17]

I suspect the real blocker isn't the bridge but the data model. The legacy schema was messy, and that made every read feel brittle regardless of connectors.

[EmmaS]

Another person on the team said it worked, then drift happened; we ended up exporting a daily CSV and feeding it in, which felt like a stopgap.