Flow Step Types: Actions

Action steps let a flow trigger something outside the current card sequence. Use them to launch another Product Fruits item, notify your team in Slack, or send an email through your existing email infrastructure.

These steps are useful when the flow should hand off to another experience, alert someone, or create a follow-up outside the product UI.

Trigger Product

Launches another published Product Fruits item when the flow reaches this step.

You can trigger a:

• Tour
• Banner
• Survey
• Another Flow

Make sure the triggered Product Fruits item is published. If it is still a draft, it will not appear for your users.

You cannot preview how the triggered item looks from within the flow editor. To test it before rolling it out, publish the flow but restrict it to yourself using targeting.

Post to Slack

Sends a message to a Slack channel when the flow reaches this step.

This requires the Slack integration to be set up beforehand. If you have not done that yet, go to [Integrations] first.

Channel

Select the Slack channel the message should go to.

Message

Write the message body.

You can include information about the user or values collected earlier in the flow using placeholders.

{{user.email}} inserts the user's email address.

{{flow.vars.<name>}} inserts any flow variable saved by a previous step.

Outbound throttling

Product Fruits caps Slack messages at 10 per minute and 200 per day per project.

If your flow hits that limit, this step is silently skipped for the users that exceed it. Keep this in mind if you are running a high-volume flow.

Send Email

Sends an email when the flow reaches this step.

Product Fruits does not send email directly. It connects to your existing email infrastructure and sends through it. This means you need to configure a sending connection before you can use this step.

Setting up a sender

Go to Add new email sender and fill in the following fields.

Name

An internal label for this sender configuration, for example Marketing server or Transactional.

This is how it will appear in the Send via dropdown when you are building a step.

Provider

Choose how Product Fruits should connect to your email service.

SMTP server: a direct connection using standard email protocol. Works with most email services and self-hosted mail servers.

SendGrid, Amazon SES, Mailgun: direct HTTP API integrations for these specific providers. If you use one of them, this is the more reliable option.

From name and from address

The sender name and email address that recipients will see.

SMTP settings

For SMTP, you will also need the following fields.

Host

Your mail server address, for example smtp.example.com.

Port

Typically 587, but your provider may use a different one.

Encryption

STARTTLS is recommended. SSL on connect is also supported.

If your server does not support either, you can select None, though this is not advisable.

Username and password

Your SMTP credentials.

For API-based providers, the username is typically your API key.

Once the fields are filled in, use Send test email to verify that the connection works before saving.

Composing the email

Send via

Select the sender configuration you set up above.

To

Enter the recipient address or addresses.

Multiple recipients can be separated by commas, semicolons, or line breaks.

Subject and body

Use the standard email subject and body fields.

Both fields support placeholders:

{{user.email}} is replaced with the current user's email at runtime.

{{flow.vars.<name>}} inserts any flow variable saved earlier in the flow.