Skip to content

Add agentic Leadbay file import flow#33

Merged
milstan merged 2 commits into
mainfrom
milstan/use-staging-mcp-backend
May 15, 2026
Merged

Add agentic Leadbay file import flow#33
milstan merged 2 commits into
mainfrom
milstan/use-staging-mcp-backend

Conversation

@milstan

@milstan milstan commented May 15, 2026

Copy link
Copy Markdown
Contributor

Adds a read-only Leadbay import resolver around the new staging /leads/resolve flow, including ambiguous candidate hydration and import-ready identity mappings. Adds custom-field creation support and exposes the import prompt/tool guidance needed for agents to preserve meaningful columns, create custom fields, expand contacts, and write notes after import. Updates import mappings to accept LEADBAY_ID, CRM_ID, and SIREN as resolver fields, with tests and changelog coverage. Verified with pnpm --filter @leadbay/core build, pnpm --filter @leadbay/core typecheck, and pnpm --filter @leadbay/mcp test -- test/prompts.test.ts.

@milstan milstan merged commit 79c5868 into main May 15, 2026
1 check passed
ArtyETH06 added a commit that referenced this pull request Jun 19, 2026
Adds workflow #33 (Modify custom fields) exercising the full
create → update → delete lifecycle, including the delete confirm-gate.
Self-contained: the scenario creates a throwaway field, renames it, and
deletes it with confirm, so the run cleans up after itself. Live run:
5/5/5/5, invariants 3/3, catalog byte-for-byte unchanged after (only the
pre-existing field remains).

Co-Authored-By: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant