Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Inbox

Email marketing and transactional email automation with INBOX (useinbox.com). Manage contacts, lists, campaigns, and react to delivery events.

CategoryMarketing
Authenticationbasic
Version0.1.0
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect Inbox with Flows360

Email marketing and transactional email automation with INBOX (useinbox.com). Manage contacts, lists, campaigns, and react to delivery events.

Use the Inbox connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 7 actions and 6 triggers.

Available actions

  • Add Contact to List
  • Create Contact List
  • Update Contact
  • Mark Contact as Unsubscribed
  • Create Campaign
  • Send Transactional Email
  • Custom API Call

Available triggers

  • New Contact
  • New Campaign
  • Email Bounced
  • Email Spam Reported
  • Email Opened
  • Email Link Clicked

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Inbox
  • Package: @activepieces/piece-useinbox@0.1.0
  • Exact artifact digest: sha256:2e393c5e5683aa7a4f926fa08b305e7c32e582578d480346e14fd64006f97087
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

BASIC AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Add Contact to List (add_contact_to_list), Adds a single contact to an INBOX contact list. Creates the contact if the email is new, otherwise updates the existing contact and ensures it is part of the list. Classification: read.
  • Create Contact List (create_contact_list), Creates a new contact list in INBOX where you can later add contacts. Classification: read.
  • Update Contact (update_contact), Updates an existing INBOX contact. You can add or replace tags and set custom field values. Classification: read.
  • Mark Contact as Unsubscribed (unsubscribe_contact), Changes a contact status to Unsubscribed so they stop receiving campaigns from INBOX. You can also mark them as Hard Bounce or Spam Reported. Classification: read.
  • Create Campaign (create_campaign), Schedules an INBOX campaign that sends a saved newsletter to one or more contact lists. Classification: read.
  • Send Transactional Email (send_transactional_email), Sends a one-off transactional email through INBOX Notify (e.g. password reset, receipt, welcome). Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Contact, polling.
  • New Campaign, polling.
  • Email Bounced, webhook.
  • Email Spam Reported, webhook.
  • Email Opened, webhook.
  • Email Link Clicked, webhook.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationbasic
Supported objects13
Supported actionsNot published
Triggers6

Authentication

Authentication method: basic

Authentication profiles

connection · basic
  • Username Required
  • Password Required · protected credential

Supported objects

ObjectReadWriteNotes
Add Contact to List Yes No Adds a single contact to an INBOX contact list. Creates the contact if the email is new, otherwise updates the existing contact and ensures it is part of the list.
Create Contact List Yes No Creates a new contact list in INBOX where you can later add contacts.
Update Contact Yes No Updates an existing INBOX contact. You can add or replace tags and set custom field values.
Mark Contact as Unsubscribed Yes No Changes a contact status to Unsubscribed so they stop receiving campaigns from INBOX. You can also mark them as Hard Bounce or Spam Reported.
Create Campaign Yes No Schedules an INBOX campaign that sends a saved newsletter to one or more contact lists.
Send Transactional Email Yes No Sends a one-off transactional email through INBOX Notify (e.g. password reset, receipt, welcome).
Custom API Call Yes No Make a custom API call to a specific endpoint
New Contact Yes No polling trigger declared by the pinned package.
New Campaign Yes No polling trigger declared by the pinned package.
Email Bounced Yes No webhook trigger declared by the pinned package.
Email Spam Reported Yes No webhook trigger declared by the pinned package.
Email Opened Yes No webhook trigger declared by the pinned package.
Email Link Clicked Yes No webhook trigger declared by the pinned package.

Triggers

New Contact · Poll

Triggers when a new contact is added to your INBOX account (through a form, manual entry, import, or API).

New Campaign · Poll

Triggers when a new campaign is created in your INBOX account.

Email Bounced · Webhook

Triggers when a transactional email permanently bounces (hard bounce) u2014 the recipient address does not exist or is blocked.

Email Spam Reported · Webhook

Triggers when a recipient marks a transactional email as spam in their inbox.

Email Opened · Webhook

Triggers each time a transactional email is opened by the recipient. Fires on every open (not unique).

Email Link Clicked · Webhook

Triggers when a recipient clicks a tracked link inside a transactional email.

Setup

Setup

  1. Add the Inbox connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-useinbox@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 7 actions and 6 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Inbox connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-useinbox@0.1.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com