Add DataForB2B plugin (dataforb2b) v0.0.1

[claude-dev-code]

Plugin Submission

Plugin information

• Author: dataforb2b
• Plugin name: DataForB2B
• Version: 0.0.1
• Source repository: https://github.com/DataForB2B/dataforb2b-dify-plugin
• Contact: contact@dataforb2b.ai

Submission type

• New plugin
• Version update

What changed

New plugin with 6 tools backed by the DataForB2B API (https://api.dataforb2b.ai):

• Search People and Search Companies — generic filter slots (column + operator + value, combined with AND/OR) plus an advanced JSON filter field.
• Enrich Profile — full profile, professional/personal email, phone, GitHub (billed only for the data types requested).
• Enrich Company — full company data (size, locations, funding, growth).
• Reasoning Search — natural-language search; an AI agent builds and runs the query.
• Typeahead — autocomplete the exact stored value for any filter.

Credentials are a single API key, validated with a credit-free GET /account call.

Risk level

• Low risk

Required checks

• I have read and followed the Marketplace submission requirements.
• I have read and comply with the Plugin Developer Agreement.
• I tested this plugin on Dify Cloud (installed the package, authorized with an API key, and ran the tools successfully). Not tested on Community Edition.
• The package contains only files needed at runtime.
• The package does not contain secrets, local credentials, .env files, .git directories, virtual environments, caches, logs, or IDE files.
• The package does not contain executables or bundled binaries.
• The plugin README includes setup steps, usage instructions, required APIs or credentials, connection requirements, and the source repository link.
• The plugin includes PRIVACY.md, and manifest.yaml references it.
• All user-facing text is in English.

Security and privacy notes

The plugin only calls https://api.dataforb2b.ai. No code/command execution, SQL, SSH, browser automation, or arbitrary URL fetching. It returns professional contact data (work/personal email, phone) only when the user explicitly requests those fields on an Enrich Profile call. The API key is stored as an encrypted Dify credential and is never logged.

Local validation

• dify plugin package ./dify — packaged successfully.
• dify plugin checksum dataforb2b.difypkg — returns a valid checksum (package decodes correctly).
• python3 -m py_compile on all tools/provider — OK.
• Live API contract verified for all 6 endpoints.
• Installed and ran on Dify Cloud.

Reviewer notes

Tested on Dify Cloud. Folder name, manifest name, and author are all dataforb2b; package built with the official dify plugin package CLI (not a manual zip).

[crazywoola]

❌ Request Changes

Decision: Request changes

Failed Checks

Check	Status	Detail	Required action
dify_plugin version	❌ Fail	dify_plugin version must be >= 0.9.0; found 0.5.1.	Use dify_plugin >= 0.9.0 in the packaged plugin environment.

Full Check Results

Check	Status	Detail	Required action
PR content language	✅ Pass	PR title/body CJK ratio=0.0% (zh=0, en=2086, ignored_zh=0, allowed_zh<=0)	None.
Project structure	✅ Pass	All expected files present: manifest.yaml, README.md, PRIVACY.md. _assets/: yes.	None.
Manifest author	✅ Pass	author is valid.	None.
Icon validation	✅ Pass	icon exists: _assets/icon.png	None.
Version check	✅ Pass	version 0.0.1 is available.	None.
README language	✅ Pass	README.md CJK ratio=0.0% (zh=0, en=2063, allowed_zh<=0)	None.
PRIVACY.md	✅ Pass	PRIVACY.md exists and is non-empty.	None.
Dependency install	✅ Pass	requirements installed successfully.	None.
dify_plugin version	❌ Fail	dify_plugin version must be >= 0.9.0; found 0.5.1.	Use dify_plugin >= 0.9.0 in the packaged plugin environment.
Install test	✅ Pass	plugin install test passed.	None.
Packaging test	✅ Pass	packaging check passed.	None.

Next steps

• dify_plugin version: Use dify_plugin >= 0.9.0 in the packaged plugin environment.

Please address these issues and push an update.

[crazywoola]

❌ Request Changes

Decision: Request changes

Failed Checks

Check	Status	Detail	Required action
dify_plugin version	❌ Fail	dify_plugin version must be >= 0.9.0; found 0.5.1.	Use dify_plugin >= 0.9.0 in the packaged plugin environment.

Full Check Results

Check	Status	Detail	Required action
PR content language	✅ Pass	PR title/body CJK ratio=0.0% (zh=0, en=2086, ignored_zh=0, allowed_zh<=0)	None.
Project structure	✅ Pass	All expected files present: manifest.yaml, README.md, PRIVACY.md. _assets/: yes.	None.
Manifest author	✅ Pass	author is valid.	None.
Icon validation	✅ Pass	icon exists: _assets/icon.png	None.
Version check	✅ Pass	version 0.0.1 is available.	None.
README language	✅ Pass	README.md CJK ratio=0.0% (zh=0, en=2063, allowed_zh<=0)	None.
PRIVACY.md	✅ Pass	PRIVACY.md exists and is non-empty.	None.
Dependency install	✅ Pass	requirements installed successfully.	None.
dify_plugin version	❌ Fail	dify_plugin version must be >= 0.9.0; found 0.5.1.	Use dify_plugin >= 0.9.0 in the packaged plugin environment.
Install test	✅ Pass	plugin install test passed.	None.
Packaging test	✅ Pass	packaging check passed.	None.

Next steps

• dify_plugin version: Use dify_plugin >= 0.9.0 in the packaged plugin environment.

Please address these issues and push an update.

[claude-dev-code]

Thanks for the review! Fixed: bumped dify_plugin to >=0.9.0,<0.10.0 in requirements.txt and repackaged with the official dify plugin package CLI. Verified locally on Python 3.12 (dify_plugin 0.9.1: imports + py_compile OK) and dify plugin checksum returns a valid checksum. The updated .difypkg is pushed to this PR.