Glossary

Explore Meshline

Products Pricing Blog Support Log In

Ready to map the first workflow?

Book a Demo

Glossary / Evaluation and implementation guide

Custom Connector

A custom connector is an integration you build, or commission, for a system the vendor does not support with a prebuilt connector.

It typically wraps the target system's API into the platform's connector framework, handling authentication, operations, and data mapping yourself.

A practical example

Example: your legacy ERP has no marketplace connector. Your team builds one that exposes three operations, query orders, update status, and create notes, then maps ERP fields to the automation platform's contact and deal objects.

What to evaluate before investing

  • Ask whether the platform offers a documented connector SDK or framework, and what languages and hosting it requires.
  • Check who owns and maintains the connector: does the vendor update it when their API changes, or is that your team's burden?
  • Confirm whether custom connectors count against plan limits, such as a maximum number of active integrations.

Limitations and tradeoffs

Custom connectors shift maintenance to you: every API change in the target system becomes your upgrade project.

They also concentrate risk in one team's knowledge, so documentation and handover plans matter more than for prebuilt options.

Plan your next step with MeshLine

Connect this decision to your automation, organic marketing and customer lifecycle management. In a MeshLine demo, discuss your existing tools, the scope you need and how to measure the result.