feat(wiza): add Wiza integration for B2B prospect enrichment and search

[waleedlatif1]

Summary

• Add Wiza integration with 5 operations: prospect search, company enrichment, get credits, start individual reveal, get individual reveal
• API key auth, async reveal pattern (start → poll), enrichment levels (none/partial/phone/full)
• Docs page with manual intro + usage sections covering async pattern and credit monitoring

Type of Change

• New feature

Testing

Tested manually

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		May 19, 2026 6:35pm

[cursor]

PR Summary

Medium Risk
Adds a new external API integration with API-key auth and multiple networked operations; main risk is request/response schema mismatches or unexpected API error handling impacting workflows.

Overview
Adds a new Wiza integration end-to-end: new WizaBlock with API-key auth and operation-specific inputs, wiring into the blocks registry, integrations metadata, and icon mappings (including a new WizaIcon).

Implements five new Wiza tools (wiza_prospect_search, wiza_company_enrichment, wiza_start_individual_reveal, wiza_get_individual_reveal, wiza_get_credits) and registers them in the tools registry, including request construction, response transforms, and typed params/outputs.

Updates docs by adding a new tools/wiza.mdx page and listing it in meta.json, and clarifies Google Docs write semantics plus a markdown toggle description for create.

^{Reviewed by Cursor Bugbot for commit 8ad7d0e. Configure here.}

[greptile-apps]

Greptile Summary

This PR adds a complete Wiza integration for B2B prospect enrichment and search, introducing 5 tools (wiza_prospect_search, wiza_company_enrichment, wiza_start_individual_reveal, wiza_get_individual_reveal, wiza_get_credits), a matching block config, icon, and documentation page.

• Tool layer (apps/sim/tools/wiza/): Each tool follows the established pattern — API key auth via user-only visibility, transformResponse with a data envelope extraction, typed params and outputs.
• Block layer (apps/sim/blocks/blocks/wiza.ts): Multi-operation block with a params function that parses JSON filter strings and coerces the size field, routing to the correct tool based on the operation dropdown.
• Docs + registry wiring: Icon, icon-mapping, integrations JSON, tools/blocks registry, and MDX docs are all registered correctly in alphabetical order.

Confidence Score: 4/5

Safe to merge with one outstanding fix needed in get_credits.ts.

The integration is well-structured and the two previously-reported issues have been addressed. The remaining concern in get_credits.ts — reading data.credits directly instead of first unwrapping the data envelope — means the Get Credits operation would silently return all-null credit fields if the endpoint follows the same response shape as the other Wiza endpoints.

apps/sim/tools/wiza/get_credits.ts — response-parsing diverges from the envelope pattern used by all other Wiza tools.

Important Files Changed

Filename	Overview
apps/sim/tools/wiza/get_credits.ts	Response-parsing differs from every other Wiza tool: reads data.credits directly from the top-level JSON rather than first extracting the data envelope. If the /api/meta/credits endpoint wraps its payload in {"data":{...}} like the other endpoints do, all four credit fields will silently be null on every call.
apps/sim/tools/wiza/start_individual_reveal.ts	Correctly builds the individual_reveal body with truthy guards; output id typed as number while the polling tool expects string — coercion is applied at the URL-build step in get_individual_reveal.
apps/sim/tools/wiza/prospect_search.ts	Clean implementation: filters object short-circuits individual filter params, size is clamped to [0,30], and the data envelope is correctly extracted before reading total and profiles.
apps/sim/tools/wiza/get_individual_reveal.ts	Correctly uses String(params.id).trim() in the URL builder; extracts the data envelope consistently with other tools.
apps/sim/blocks/blocks/wiza.ts	Block correctly wires all 5 operations; params function parses JSON filter strings and coerces size to a number.
apps/sim/tools/wiza/company_enrichment.ts	Consistent with other tools; extracts the data envelope correctly and applies truthy guards before adding optional identifiers to the request body.
apps/sim/tools/wiza/types.ts	Types are well-structured; enrichment_level is correctly narrowed to a union literal.

_{Reviews (4): Last reviewed commit: "fix(wiza): throw on invalid JSON in adva..." | Re-trigger Greptile}

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 8ad7d0e. Configure here.}