Trigger campaigns in journeys
Trigger email and SMS from journey Destination nodes using GrowthLoop Channels or composable destinations like Iterable, SFMC, and SendGrid.
From a journey Destination node you can trigger email and SMS in two ways: send through GrowthLoop Channels, or trigger a campaign in a composable destination such as Iterable, Salesforce Marketing Cloud, or SendGrid.
Both paths use the same journey canvas. The difference is who sends the message and where the creative lives.
Prerequisites
- A published or draft journey
- Either:
- A GrowthLoop Email or GrowthLoop SMS destination with a channel configuration — see Configure email and SMS channels, or
- A connected composable destination (Iterable, SFMC, SendGrid, and so on)
- Templates or campaigns ready in Content Library and/or the destination platform
Compare the two paths
| GrowthLoop Channels | Composable destinations | |
|---|---|---|
| Destination type | GrowthLoop Email / GrowthLoop SMS | Iterable, SFMC, SendGrid, etc. |
| Who sends | GrowthLoop | The external platform |
| Content choices | Local content from Content Library | Local content, Destination content, and Campaigns |
| Typical setup | Channels + per-team destination | Platform credentials on the destination |
| Publish into platform | Not applicable (GrowthLoop is the sender) | Optional — publish Content Library templates into the platform |
Path A: Send with GrowthLoop Channels
- Open your journey and drag in a Destination node.
- Click Select a Destination and choose your GrowthLoop Email or GrowthLoop SMS connection.
- Set an Export Name.
- Choose the send action (for example Send Email or Send SMS).
- Select a template from Local content in the content picker (Content Library).
- Map match fields (for example recipient email) and any personalization fields required by the configuration.
- For email, choose the sender options when prompted.
- Click Save.
[Screenshot: Destination node configured for GrowthLoop Email with Local content selected]
NoteGrowthLoop Email and SMS do not show platform-native Destination content tabs the way Iterable or Salesforce Marketing Cloud do—creative lives in Content Library.
Path B: Trigger a composable destination campaign
This is the Engagement Suite replacement for the former Composable Campaigns flow (including SendGrid Send Email).
- Open your journey and drag in a Destination node.
- Click Select a Destination and choose your Iterable, Salesforce Marketing Cloud, SendGrid, or other composable connection.
- Set an Export Name.
- Choose a campaign action such as Send Email (instead of list-only actions like Add to List Only, when available).
[Screenshot: Destination export action set to Send Email]
- Open the template or campaign field. Refresh platform fields if the list is empty or stale.
- Pick content using one of:
- An existing platform template from the dropdown
- Pick from library to use or publish Content Library content
- The content picker tabs: Local content, Destination content, or Campaigns
- If you publish new content, complete Publish settings (content name, campaign name, subject, and platform-specific fields).
- Map recipient / match fields and personalization variables required by the template.
- Optionally send a test where the destination supports it (for example SendGrid test email).
- Click Save.
[Screenshot: Content picker with Local content, Destination content, and Campaigns tabs]
SendGrid example
For SendGrid specifically:
- Select your SendGrid destination and choose Send Email.
- Configure From Email, recipient email match field, and Email Template.
- Map warehouse fields to template variables.
- Send a test email if available, then save.
The same pattern applies to Iterable and Salesforce Marketing Cloud, with platform-specific publish fields where required.
Choose the right path
- Use GrowthLoop Channels when GrowthLoop should own delivery and you want Content Library as the system of record for creative.
- Use composable destinations when creative, compliance, or deliverability already live in Iterable, SFMC, or SendGrid and you want GrowthLoop to orchestrate who enters the campaign.
- Mix both in one journey when different steps should send through different systems.
Congrats—you can trigger campaigns from journeys!
Next, dive into using external templates and campaigns, or assign AI variants with decisioning.
NoteExperiencing any issues? Reach out to us at [email protected] and we'll help resolve the matter.
Updated 3 days ago