What needs to happen in your app before a workflow can start?

Decide what action the app can report reliably, such as “first project created.” Customer.io can start a workflow from an event or use a segment, a group of people who match a rule. Your app needs to send the event or update the facts the rule uses.

How do you keep a product tip inside the permission someone chose?

Map the tip to an email topic in the subscription center. Topic preferences govern the subject and channel preferences govern how the message arrives. If a topic should require explicit permission, set it up as unsubscribed by default. Check both the workflow and any message-level overrides before it runs.

What is a billable profile, and what can you move?

Essentials currently starts at US$100 per month with 5,000 profiles and one million monthly emails. A profile can be a person or a tracked object, such as a company. The plans have overages. Billing counts email that reaches the sending provider, including mail the provider bounces or suppresses.

Export people and selected attributes as CSV, or use the single-person export for more detail. Check global and topic choices separately. The CSV importer supports setting subscription preferences. Keep the event definitions and workflow logic outside the export so you can rebuild them.

Who should get a reminder to create a first project?

Make a paper table with three fictional signups. Compare someone who finished setup, someone who still needs help, and someone who opted out of tips.

Check the action
Exclude the person with a first-project event from the reminder.
Check the permission
The unfinished signup qualifies only if the tip topic and email channel allow it.
Check the quiet path
The opted-out person should remain excluded even if their setup is unfinished.