mirror of https://github.com/Significant-Gravitas/AutoGPT.git synced 2026-02-05 20:35:10 -05:00

Files

Nicholas Tindle 90466908a8 refactor(docs): restructure platform docs for GitBook and remove MkDo… (#11825 )

<!-- Clearly explain the need for these changes: -->
we met some reality when merging into the docs site but this fixes it
### Changes 🏗️
updates paths, adds some guides
<!-- Concisely describe all of the changes made in this pull request:
-->
update to match reality
### Checklist 📋

#### For code changes:
- [x] I have clearly listed my changes in the PR description
- [x] I have made a test plan
- [x] I have tested my changes according to the test plan:
  <!-- Put your test plan here: -->
  - [x] deploy it and validate

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> Aligns block integrations documentation with GitBook.
> 
> - Changes generator default output to
`docs/integrations/block-integrations` and writes overview `README.md`
and `SUMMARY.md` at `docs/integrations/`
> - Adds GitBook frontmatter and hint syntax to overview; prefixes block
links with `block-integrations/`
> - Introduces `generate_summary_md` to build GitBook navigation
(including optional `guides/`)
> - Preserves per-block manual sections and adds optional `extras` +
file-level `additional_content`
> - Updates sync checker to validate parent `README.md` and `SUMMARY.md`
> - Rewrites `docs/integrations/README.md` with GitBook frontmatter and
updated links; adds `docs/integrations/SUMMARY.md`
> - Adds new guides: `guides/llm-providers.md`,
`guides/voice-providers.md`
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
fdb7ff8111. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: claude[bot] <41898282+claude[bot]@users.noreply.github.com>
Co-authored-by: bobby.gaffin <bobby.gaffin@agpt.co>

2026-01-23 06:18:16 +00:00

1.3 KiB

Raw Blame History

Zerobounce Validate Emails

Blocks for validating email deliverability using ZeroBounce.

Validate Emails

What it is

Validate emails

How it works

This block uses the ZeroBounce API to validate email addresses for deliverability. It checks if an email is valid, invalid, catch-all, spamtrap, abuse, or disposable. Optionally provide an IP address for additional validation context.

The response includes detailed status information, SMTP provider, and recommendation on whether to send emails to that address.

Inputs

Input	Description	Type	Required
email	Email to validate	str	Yes
ip_address	IP address to validate	str	No

Outputs

Output	Description	Type
error	Error message if the search failed	str
response	Response from ZeroBounce	Response

Possible use case

List Cleaning: Validate email lists before campaigns to reduce bounce rates.

Lead Qualification: Verify lead email addresses as part of intake workflows.

Form Validation: Check email validity in real-time during user registration or contact form submissions.

1.3 KiB Raw Blame History