01 What happened
The author of the blog post introduced the Custom Discovery Connector (CDC), letting users pull data from any API endpoint directly into LeanIX without running a script outside their workspace. The connector follows three steps: Build (AI-assisted code generation), Map (fact sheet type and field mapping), and Review & Push (staged review). The blog demonstrates how CDC can surface SaaS applications that SaaS Discovery marked as rejected or unknown, supporting enterprise architects hunting for shadow IT.
02 Key details
- The author of the blog post introduced the Custom Discovery Connector (CDC), enabling data ingestion from any API endpoint without external scripts.
- The three-step process uses AI to generate fetch code, allows manual mapping to fact sheet fields, and provides a staged review area before inventory updates.
- The GET /discoveries endpoint was extended to return SaaS applications marked 'rejected' or 'unknown' by SaaS Discovery, which were previously unavailable.
- A ~70-line example connector fetches rejected and unknown SaaS items, maps them to Application fact sheets, and lets users decide which to promote.
03 Why it matters
Data not covered by ready-made integrations previously required custom scripts or manual work. CDC lowers the barrier by letting users describe sources in plain language and have AI generate the fetch code. The extended GET /discoveries endpoint also exposes previously inaccessible rejected or unknown SaaS data, helping enterprises spot shadow IT and manage unregistered applications.
04 Who it matters to
SAP customers, SAP integration teams, SAP developers and SAP system administrators.