- Brand
- Unknown
- Category
- Pending
- Primary Subcategory
- Email & SMS Lifecycle Marketing Automation
Integration details
Description
Banger helps you manage company email across the products in your connected workspace: create email designs, send Product email and marketing campaigns, build Journeys, read Mailboxes and send emails, and manage contacts and consent. Requested routine actions execute directly under workspace policy. Journey activation requires review of the exact sending definition; approved unchanged Journeys then run automatically. Delivery reports distinguish queued, sent, delivered, and failed states.
- Integration type
- Plugin
- Verification status
- Not applicable
- Platform
- ChatGPT
- Category
- Pending
- Primary Subcategory
- Email & SMS Lifecycle Marketing Automation
- Secondary Subcategories
- None listed
- Brand
- Unknown
- Access
- Account required
- First tracked
- 2026-10-29
- Tool count
- 285
- Market
- US
The broad Category that contains the Primary Subcategory.
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Your score is coming
ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.
What discovery looks like

Get alerts for Banger
Get updates when Banger’s Discoverability Score or category rank changes.
Competing in ChatGPT Email & SMS Lifecycle Marketing Automation
View Category285 tools agents can invoke
Activate or resume one saved Journey for automatic email delivery. Requires the existing human sending review; otherwise returns a pending review request. Does not accept a workflow, operation selector or arbitrary action. Sending requires human review and is limited to the saved definition and audience scope.
banger_activate_journey
Add one label to a thread; its other labels stay.
banger_add_thread_label
Add existing product contacts to a product list by identifier; consent and suppression are preserved. Safe retries return canonical membership read-back.
banger_add_contact_list_members
Create inboxes on the saved domain from local names, such as hello and support. They stay pending until verification succeeds. Hosted mailboxes send only to themselves, the signup address, or other hosted mailboxes in the same product. Part of the guided setup shared with the Banger web app; repeating it resumes saved progress.
banger_onboarding_add_inboxes
Prepare one chosen lane and its exact DNS bundle, without extra sibling lanes or DNS changes. Mail is the default connection for receiving and all email types. Product and Broadcast are optional dedicated sending lanes. domain is the company domain; from_domain is the exact root or subdomain. Existing MX, SPF, DKIM, and DMARC are preserved. Conflicts at Banger’s receiving or return-path names require a signed-in administrator's migration review. dns_bundle.status reports whether the complete provider records are prepared. Pending status may mean DNS propagation.
banger_create_email_lane
Archive one Journey and stop its future steps. Preserve its history.
banger_archive_journey
Archive a Broadcast (archived=true) to hide it from the Broadcast list while keeping its recipients, statistics, Logs, and unsubscribe links, or restore it (archived=false). Applies to Broadcasts that sent; unsent ones can be deleted instead. Not allowed while scheduled, sending, or paused.
banger_archive_broadcast
Archive a thread out of the inbox, or bring it back with archived=false. Nothing is deleted.
banger_archive_thread
Record a domain for this product and use its first reported domain as an initial brand-discovery source. This does not configure sending or change DNS; several products may report the same domain.
banger_add_product_domain
Assign a thread to one teammate, replacing any current assignee, or unassign it with identity_id null.
banger_assign_thread
Cancel a draft, scheduled, sending, or paused Broadcast. Irreversible: a cancelled Broadcast cannot be resumed or sent again, and pending recipients are dropped (recipients already sent stay sent). Pausing is the reversible alternative. Returns the Broadcast read-back (status cancelled).
banger_cancel_broadcast
Sets another workspace member's role to admin, member or viewer. Admins hold workspace administration (invite people, rename the workspace, connect providers, create API keys), though only the owner can delete the workspace; members read and send mail and work with contacts and campaigns; viewers only read. Requires a workspace owner or admin acting through a person's authorization, not a standalone API key. Nobody can change their own role, and the owner's role cannot be changed. The result returns the member with role and previousRole; setting the role a member already has changes nothing.
banger_set_member_role
Read-only availability and DNS preflight for one exact hostname and Mail (mailbox), Product, or Broadcast. Supports the root or a subdomain. Returns existing lane identifiers, occupied hostname conflicts, detected email DNS, and records that conflict with the exact receiving or return-path names. Website records alone leave email setup available.
banger_plan_email_lane
Read actionable blockers for footer identity/address, canonical Broadcast route, consent/suppression, selected audience, personalization, sending allowance, and automatic or human approval requirements. Does not send test messages or freeze recipients. Send-time controls remain authoritative.
banger_check_broadcast_readiness
Check the saved DNS records in public DNS and update verification. Records may take time to propagate; pending is not an error. Changes no DNS records. Part of the guided setup shared with the Banger web app; repeating it resumes saved progress.
banger_onboarding_verify_dns
Choose what Banger does for the domain: simple (the default: Banger sends and receives on the chosen mailbox address), send_only (Banger sends; the current inbox provider keeps receiving), or send_and_receive (Banger sends and also receives, set up separately). Changing it restarts DNS progress. Part of the guided setup shared with the Banger web app; repeating it resumes saved progress.
banger_onboarding_choose_delivery
Name and configure a Journey Banger discovered from raw API sends. Saving a draft sends nothing and needs no review; a Journey's first activation needs one human review of its sending setup.
banger_claim_journey
Verify that a file uploaded to its signed URL exists with its declared size and media format, and mark the attachment ready. Only ready attachments can be submitted. Up to five files per report within 24 hours; attachments belong to the uploading user and workspace and cannot be reused on another report.
banger_complete_feedback_attachment
Reconcile the connection checkpoint when an authorized OAuth connection still appears pending. Normal OAuth authorization completes the checkpoint automatically. Idempotent; changes no mailbox, DNS, sending, Journey, Broadcast, or billing state, and returns no credentials.
banger_confirm_connection
Send a message to Banger support. A person on the Banger team reads it and replies by email to the signed-in person's verified address, usually the same day. Suited to questions about using Banger, account or billing help, and problems that persist after retrying; bug reports and feature ideas have their own feedback tools. The workspace, plan and connected client are attached automatically. Returns status and reply_to, the address the reply goes to.
banger_contact_support
Move on to adding inboxes while DNS verification continues; does not mark verification complete. Part of the guided setup shared with the Banger web app; repeating it resumes saved progress.
banger_onboarding_continue_to_inboxes
One-way conversion of a paused or draft legacy Journey using HTML/Liquid already prepared by your migration skill. Supply contract only for a single-email Journey, or step_contents with exactly one contract per email step, including split arms. Banger does not import or execute TSX/MJML. Creates managed drafts and requests publication review; nothing is sent.
banger_convert_journey_to_managed
Create an idempotent native mailbox on a workspace sending domain. It remains pending until the domain, stream, and inbound MX are verified.
banger_create_native_mailbox
Create an isolated email operating scope for one product, store, brand, newsletter, or company, with its own audiences, domains, Mailboxes, Broadcasts and Journeys.
banger_create_product
Create or resume a Banger-hosted mailbox without a company domain. create_new:true creates an additional mailbox. Its address is <local_part>@bangermail.com when a name is given, otherwise a friendly word name such as quiet-maple-harbor. Every hosted mailbox can send only to itself, other hosted inboxes in the same product, and the workspace signup email, including To, Cc and Bcc; hosted inboxes in another product or workspace are not allowed. A connected custom domain is required to send to other recipients.
banger_create_starter_mailbox
Save one draft Journey definition. This only stores configuration; activation and enrollment are separate operations. Supports only email, wait, contact-condition and split records; step names are customer-facing. A monitored wait is kind=wait with config={amount:3,unit:"days",until:{name:"Registration completed",path:"attributes.registered",operator:"equals",value:true},on_met:"continue"}; on_met is required: continue (skip the following reminder email and proceed) or end_journey (complete this Journey), and the reminder email is the following sibling step. A contact without the field has not reached the milestone, so the reminder sends; integrations only need to report what happened. Checks use current contact data about once per minute. Milestones map to verified contact data, not eligibility flags. Each person enters once by default; trigger.config.once_per_person=false lets people re-enter after they finish, optionally after trigger.config.reentry_days. An email step config takes one content source, the same shapes a Broadcast stores: template_id (a saved design) with content_overrides filling its slots; or the step's own design as subject, body_html, body_text and content_overrides; or managed_content_id. delivery_class is product or broadcast. Drafts may leave a button link empty; activation and send report it. Saving a draft sends nothing and needs no review; a Journey's first activation needs one human review of its sending setup.
banger_create_journey
Create a Triage rule for incoming mail in one mailbox. When: description (judged by Jev), exact_conditions, and/or has_label_ids (all given have to hold). Then: actions (apply_label, archive, mark_read, star). Every plan has Triage; plans differ in how many rules can be on and how many emails are triaged per month.
banger_create_triage_rule
Create a Banger label in one mailbox. suggestion_id creates a suggested label (auto-set turns on when the plan's Triage rule amount has room). Optionally sets emoji and auto_set. Creating an existing name returns the existing label. Banger labels are not synced to Gmail.
banger_create_label
Save an email draft in one mailbox, as a person would in Mailboxes: recipients, subject and body, optionally as a reply in an existing thread. Nothing is sent; the draft waits in the mailbox until someone sends it.
banger_create_mail_draft
Create a client ID and client secret for an agent platform that adds Banger as a custom MCP server with OAuth, such as Gemini Enterprise. The gemini_enterprise preset (the default) uses Google's redirect URI; custom takes the platform's HTTPS redirect URIs. Each member who connects through the client signs in to Banger and approves it, and acts with their own role in this workspace. The result lists the client ID and the values for the platform's form (server URL, authorization URL, token URL, scopes); the one-time secret appears in the private credential card attached to this result in an MCP Apps host, outside model context, and can also be created in Banger's Settings, Connected apps. Not idempotent: each call creates another client; revoke one whose secret was lost.
banger_create_oauth_client
Save a reusable email design. {{placeholders}} mark fill-in content whose values go in content; recipient fields use {{first_name|there}} style placeholders with fallbacks. Designs carry the product brand. Nothing is sent. Saving a draft sends nothing and needs no review; a Journey's first activation needs one human review of its sending setup.
banger_create_template
Create an incoming endpoint and its durable Banger connection for an approved product integration. Returns connection_id for Journey triggers. The private credential panel shows a secret URL, or a public URL with a separate Authorization: Bearer token; credentials stay outside model context. Requires an MCP Apps host; Banger's Webhooks page offers the same. Supabase auth hooks use the secure Banger setup page. Does not activate Journeys or prove event receipt. Not idempotent: each call creates another webhook.
banger_create_incoming_webhook
Create an outbound endpoint that receives signed Banger events for one product, as the Webhooks page does. event_types picks the events; omit it for the default activity events. Specific events (mail.received, mail.sent, send.delivered, send.bounced, send.complained, journey.enrolled, journey.completed, journey.exited) carry the ids an automation needs and are sent only when chosen. The private credential panel shows the signing secret once; it stays outside model context. Requires an MCP Apps host; Banger's Webhooks page offers the same. Not idempotent: each call creates another webhook, and each name is unique per product.
banger_create_outgoing_webhook
Create an editable Broadcast draft from source-only managed content or a saved product design and mailbox. Managed source creates a reviewed draft and queues missing languages for free translation. Each recipient gets it in their own language: readers of a language still translating get it once their translation is ready, and are skipped (error_code translation_failed, translation_awaiting_review or translation_still_preparing) if it is not ready within a day of sending. Empty audience drafts are allowed; sends stay blocked until eligible recipients and a published source are ready. Omit mailbox_id to use the existing product default sender, preferring the chosen custom-domain address. Requires a retry key and returns canonical read-back. Saving a draft sends nothing and needs no review; a Journey's first activation needs one human review of its sending setup.
banger_create_broadcast
Declare a contact field before data arrives, so imports, forms and the API store it in the right type under a clear label. key defaults from the label ("Team size" becomes team_size). choice and choices fields can list their allowed options.
banger_create_contact_field
Create one product contact list with safe retries and canonical read-back. Does not import or subscribe contacts.
banger_create_contact_list
Create a shared layout draft. Without html it is seeded from the existing product brand. The HTML contains exactly one {{ content }} slot. Does not publish.
banger_create_layout
Create source-only managed content. Nothing is sent or published. Missing configured languages are queued for free background translation, so not every variant needs to be supplied.
banger_create_managed_content
Save a product contact segment, with safe retries and canonical preview read-back. Does not create consent. filter.conditions are typed checks on contact fields (each contact field lists the operators its type allows): {field, op, value} with op is, is_not, contains, set, not_set, gt, gte, lt, lte (numbers and dates), within_days (dates, value = days), any_of (value = list), includes (several-choice fields). filter.match is all (default) or any. status and exact attributes also work.
banger_create_segment
Signup forms grow a product list from the person's own site: inline card, popup (delay/scroll/exit-intent triggers), bar, corner slide-in, or a hosted page (a link for bios and posts). Widgets wear the product brand and email style, so signups get matching email. Double opt-in is on by default: a branded confirmation email is sent and people join the list only after confirming; consent evidence is recorded. Banger's own words (defaults left untouched, messages, the confirmation email, the confirmed page) appear in the visitor's language (English, Portuguese, Spanish, French, German), or in config.locale when set; copy the person writes stays exactly as written. config.fields adds up to 6 extra questions (text, select with options, or checkbox; optional required); answers are saved on the contact under each field's key (derived from the label when omitted), usable in segments and personalization. Bars ask for email and optionally a first name (config.collect_name); custom questions (config.fields) are not shown on bars. Forms can be created and set live only once the product has a verified sending domain (otherwise 409 verified_domain_required). Creates a form. list_id selects a list; list_name uses or creates a list by name (default "Newsletter"). config is partial: omitted settings use defaults for the kind; headline, body and button_label are the form's own copy. style empty follows the brand's email style. Returns embed_code and hosted_url. Requires a retry key.
banger_create_signup_form
Stop all Mailboxes, Product, and Broadcast delivery for one domain and queue Banger-owned provider teardown. Message history and audit records are preserved. The exact root domain is required as confirmation.
banger_delete_native_sending_domain
Permanently delete a webhook, as the Webhooks page does, so its name can be used again. An outbound endpoint's delivery history is deleted with it. An incoming webhook is deleted with its connection, and only while no Journey, archived ones included, has that connection as its trigger or goal; otherwise the webhook_in_use error lists those Journeys. Unlike disabling, deleting cannot be undone. Retrying after the webhook is gone returns deleted with replayed=true.
banger_delete_webhook
Delete a Triage rule. A label's auto-set rule is removed by turning auto-set off or deleting the label.
banger_delete_triage_rule
Delete a Banger label. Its auto-set rule is deleted with it, it is removed from threads, and other Triage rules stop applying it.
banger_delete_label
Permanently delete a Broadcast that has not sent to anyone (a draft, or one cancelled or failed before any recipient was sent) together with its own design. A Broadcast that sent cannot be deleted, only archived. A scheduled, sending, or paused Broadcast is refused until it is cancelled. Irreversible.
banger_delete_broadcast
Permanently deletes only the selected mailbox and its Banger messages, attachments, drafts, labels and triage. Requires the preview_token and exact confirm_address from the mailbox's deletion preview, once the person has reviewed its impact and dependent sending flows and explicitly confirmed the exact address; a mailbox whose state changed needs a new preview and a new confirmation. Cancels queued sends and unfinished Broadcasts, pauses dependent Journeys and signup forms, and keeps sending history and billing records. The domain, other mailboxes and Gmail's original inbox are kept. A confirmed request retried with the same idempotency_key deletes once.
banger_delete_mailbox
Delete a product contact segment. Refused while a Broadcast that hasn't sent yet or a Journey that isn't archived still uses it as its audience; the error names them. Sent Broadcasts keep their frozen audience. Contacts are not deleted.
banger_delete_segment
Have Banger's backend inspect public DNS and the company website. Returns the authoritative DNS provider, existing email services, and the canonical recommended connection plan. Discovery does not indicate DNS readiness.
banger_onboarding_discover_domain
Copy a saved design (template) into a new active design with the same subject, HTML, text, fill-in content, and slots, as the Designs page's Duplicate does. name defaults to "<name> copy". Returns the new design. Not idempotent: each call creates another copy.
banger_duplicate_template
Disable a webhook (status=disabled) or turn a disabled or failing one back on (status=active), as the Webhooks page does. Disabling keeps the webhook, its name and its history. Disabling an incoming webhook also disables its connection, so Journeys triggered by it stop receiving events until it is re-enabled; disabling an outbound one stops deliveries. Returns the webhook read-back; retrying when it already has that status returns its current state.
banger_set_webhook_status
Banger ChatGPT Plugin FAQ
How the directory, categories and Discoverability Score work.
Read the methodologyHow do I improve Banger's ChatGPT Plugin discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are Banger alternatives on ChatGPT?
As of 2026-10-29, Banger competes with ActiveCampaign, Aivie, AWeber, beehiiv, Bizgo, Brevo, Conversion, Customer.io and 44 more in ChatGPT Email & SMS Lifecycle Marketing Automation, ranked by public Discoverability Score.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.