Keep consent explicit
Collect a separate marketing opt-in in your own signup or preference flow.
Integrations Kit (formerly ConvertKit)
Kit (formerly ConvertKit)Planned
Kit (formerly ConvertKit)PlannedUseful support. Permission-based follow-up.
Plan your Kit (formerly ConvertKit) integration with Message. Plan a custom Kit workflow around explicit subscriber consent. A support conversation should never silently become a marketing subscription.
Native connector planned. There is no native Kit connector or automatic subscriber sync in Message today.
Email marketing
What we’re planning to connect.
- 01Approved opt-in
- 02Your automation
- 03Kit audience
Preserve subscriber choices
Check existing subscriber status before applying a tag or enrolling anyone in a sequence.
Coordinate follow-up
Use your own approved customer mapping to connect a support outcome with a relevant follow-up campaign.
The right context
Be precise about what connects.
Define the data, permissions and destination before putting the workflow in front of customers.
Identity
Use a verified customer mapping from your own system. Message automation polling does not return email addresses.
Subscriptions
Opt-in source, time and withdrawal state must be handled by your workflow.
Writes
Any Kit subscriber or tag changes need separate authorization and implementation.
Prepare for the connection
Define your first workflow.
- 01
Choose one audience
Identify the Kit account, audience workflow and consent source.
- 02
Build the mapping
Use the Kit API and your own customer identifier mapping. Store credentials on the server.
- 03
Test unsubscribe behavior
Verify opted-in, unsubscribed and unknown contacts. Do not reactivate an unsubscribed contact from a support event.