Workflows

A workflow is the sequence of steps 1eyeᴬᴵ follows to engage target contacts from a Target List. It controls which channel is used, what message is sent, who sends it, how long to wait, which signals to check, and what happens next.

Use Workflows to build campaign logic across Email, LinkedIn, and iMessage.

What Workflows are for

Workflows help your team answer:

What should happen next for each target contact

What should happen next for each target contact

What should happen next for each target contact

A campaign workflow can send messages, wait between steps, check signals, branch based on activity, and stop when the campaign reaches an end state.

Use Workflows to:

1. Send email messages

2. Send LinkedIn connection requests

3. Send LinkedIn messages

4. Send iMessages or SMS fallback messages

5. Add wait time between steps

6. Check signals

7. Branch into Yes or No paths

8. Personalize messages by ICP

9. Personalize messages by persona

10. End the campaign path cleanly

How Workflows work

A workflow usually starts with a Start node and ends with an End node.

Between Start and End, you can add action nodes and signal nodes.

Example:

Start
↓
Email: Intro Email
↓
Wait 1 Day
↓
LinkedIn: Connection Request
↓
Signal: If LinkedIn accepted
   Yes → LinkedIn: Send Message
   No → Email: Final Email
↓
End

Start
↓
Email: Intro Email
↓
Wait 1 Day
↓
LinkedIn: Connection Request
↓
Signal: If LinkedIn accepted
   Yes → LinkedIn: Send Message
   No → Email: Final Email
↓
End

Start
↓
Email: Intro Email
↓
Wait 1 Day
↓
LinkedIn: Connection Request
↓
Signal: If LinkedIn accepted
   Yes → LinkedIn: Send Message
   No → Email: Final Email
↓
End

This lets 1eyeᴬᴵ run a structured sequence instead of sending one-off messages.

Workflow canvas

The Workflow tab gives you a visual canvas for campaign logic.

On the canvas, you can:

1. View all workflow nodes

2. Add new nodes

3. Select a node to configure it

4. Connect steps in order

5. Add waits

6. Add signal conditions

7. Branch paths

8. Save workflow changes

9. Open the Console when the campaign is running

Each node represents one step in the campaign.

Workflow nodes

Common workflow nodes include:

Only channels that are enabled and connected will be available for channel nodes.

Start node

The Start node begins the campaign workflow.

It represents the entry point for target contacts in the selected Target List.

The Start node is usually created automatically when the campaign workflow is created.

Use the Start node to understand which campaign or target list the workflow is attached to.

End node

The End node stops the workflow path.

A contact reaches End when there are no more steps for that path.

Use End nodes to close the campaign flow after:

1. A final message

2. A completed branch

3. A signal condition path

4. A follow-up sequence

5. A no-action path

Every workflow path should eventually lead to an End node.

Channel nodes

Channel nodes send messages.

1eyeᴬᴵ supports these campaign channel nodes when enabled:

1. Email

2. LinkedIn

3. iMessage

Each channel node needs the right sender or line selected before it can run.

If a channel is not available, check:

1. Workspace plan

2. Engagement channel enablement

3. User account connection

4. Sender availability

5. Contact data availability

Email node

An Email node sends an email from a connected Google Workspace Gmail mailbox.

Email nodes can be used for:

1. Intro emails

2. Follow-up emails

3. Final emails

4. ICP-specific emails

5. Persona-specific emails

6. Re-engagement messages

An Email node typically includes:

1. Email type

2. Sender

3. Subject

4. Body

5. Message personalization option

6. Wait time

7. Save and test options when available

Email type

Email type describes the purpose of the email step.

Examples:

Intro Email
Follow-up Email
Final Email

Intro Email
Follow-up Email
Final Email

Intro Email
Follow-up Email
Final Email

Use clear email types so the workflow is easy to understand later.

Email sender

Each Email node needs a sender.

The sender must have a connected Google Workspace Gmail mailbox.

If no sender appears, check:

1. Email is enabled in Settings → Engagement Channels

2. The workspace is on a paid plan

3. The user has connected a Google Workspace Gmail mailbox

4. The mailbox shows Connected

5. The mailbox is within send limits

Email subject

Email nodes require a subject line.

The subject should be clear, relevant, and short.

Good examples:

Quick idea for Snowbricks
Improving account intelligence
Signal-led GTM workflow

Quick idea for Snowbricks
Improving account intelligence
Signal-led GTM workflow

Quick idea for Snowbricks
Improving account intelligence
Signal-led GTM workflow

Avoid vague or spammy subjects.

Weak examples:

Huge opportunity!!!
Important
Please read

Huge opportunity!!!
Important
Please read

Huge opportunity!!!
Important
Please read

Email body

The body is the main email message.

A good email body should:

1. Be concise

2. Reference the target contact or company when relevant

3. Explain why you are reaching out

4. Connect to the campaign purpose

5. Include a clear next step

6. Avoid sounding generic

LinkedIn node

A LinkedIn node sends a LinkedIn connection request or LinkedIn message from a connected LinkedIn account.

LinkedIn nodes can be used for:

1. Connection requests

2. Messages after a connection is accepted

3. Follow-up messages

4. Persona-specific LinkedIn messages

5. ICP-specific LinkedIn messages

6. Multi-channel reinforcement

A LinkedIn node typically includes:

1. LinkedIn type

2. Sender

3. Message body

4. Message personalization option

5. Wait time

LinkedIn type

LinkedIn type defines what action the node performs.

Common types include:

Connection Request
LinkedIn Message

Connection Request
LinkedIn Message

Connection Request
LinkedIn Message

Use Connection Request when the target contact is not yet connected.

Use LinkedIn Message when the workflow should send a message to a contact that can receive LinkedIn messages.

LinkedIn sender

Each LinkedIn node needs a sender.

The sender must have a connected LinkedIn account.

If no sender appears, check:

1. LinkedIn is enabled in Settings → Engagement Channels

2. The workspace is on a paid plan

3. The user has connected LinkedIn

4. The LinkedIn account shows Connected

5. The account is within connection or message limits

LinkedIn message body

LinkedIn messages should be short and direct.

A good LinkedIn message should:

1. Feel natural

2. Be relevant to the target contact

3. Avoid sounding automated

4. Use company, persona, or signal context when useful

5. Have a simple next step

LinkedIn connection requests should usually be shorter than email.

iMessage node

An iMessage node sends a message from a connected iMessage-enabled line.

If the target contact does not have an iMessage-compatible device, the message may be sent as SMS.

iMessage nodes can be used for:

1. Direct outreach

2. Follow-up messages

3. High-intent contact follow-up

4. Persona-specific messaging

5. Multi-channel campaign steps

An iMessage node typically includes:

1. iMessage type

2. Sender line

3. Message body

4. Message personalization option

5. Wait time

iMessage sender

Each iMessage node needs a connected iMessage line.

If no sender line appears, check:

1. iMessage is enabled in Settings → Engagement Channels

2. The workspace is on a paid plan

3. An iMessage line has been requested

4. The line shows Connected

5. The target contacts have phone numbers

6. The line is within daily limits

iMessage body

iMessage messages should be short and specific.

A good iMessage should:

1. Be brief

2. Be relevant

3. Avoid long paragraphs

4. Use a clear reason for reaching out

5. Make it easy to reply

Because iMessage and SMS are direct channels, keep the message respectful and concise.

Message personalization options

Channel nodes may allow you to choose how messages are written across the audience.

Common options include:

1. Same message to all

2. Different message to each ICP

3. Different message to each persona

Use the right option based on how broad or focused your target list is.

Same message to all

Use Same message to all when the audience is narrow and the same message makes sense for every target contact.

This works best when:

1. The target list has one ICP

2. The target list has one persona

3. The campaign goal is the same for everyone

4. The message angle is consistent

Example:

All contacts are Revenue Operations Leaders at B2B SaaS companies

All contacts are Revenue Operations Leaders at B2B SaaS companies

All contacts are Revenue Operations Leaders at B2B SaaS companies

Different message to each ICP

Use Different message to each ICP when the target list includes multiple company segments.

For example, a campaign may include companies from different ICPs:

1. B2B SaaS Companies

2. Data Infrastructure Companies

3. Enterprise Sales Organizations

4. AI-Native GTM Companies

Each ICP may care about a different business problem.

Writing different messages by ICP helps the message match the company context.

Different message to each persona

Use Different message to each persona when the target list includes multiple target contact types.

For example, a campaign may include:

1. Revenue Operations Leader

2. Head of Data

3. VP Sales

4. Founder or CEO

Each persona cares about different outcomes.

A RevOps leader may care about routing, enrichment, and CRM quality.

A Head of Data may care about data quality, activation, and governance.

A Founder may care about growth, efficiency, and team leverage.

Different persona messages help avoid generic outreach.

Editing messages

When you select Edit on a message node, you can write or update the message content.

For Email, you typically need:

1. Sender

2. Subject

3. Body

For LinkedIn, you typically need:

1. Sender

2. Message body

For iMessage, you typically need:

1. Sender line

2. Message body

Make sure every message is complete before launching the campaign.

Variables

Messages may support variables.

Variables help insert contact, company, sender, or campaign context into the message.

Examples may include:

1. First name

2. Company name

3. Title

4. Industry

5. Sender name

6. Signal context when available

Use variables carefully.

A good variable makes the message more relevant.

A broken or missing variable makes the message feel automated.

Test messages

When available, use test message options before launch.

Testing helps confirm:

1. Sender is selected

2. Subject looks right

3. Variables render correctly

4. Message body is formatted correctly

5. Links work

6. The message does not look broken

Do not launch a campaign without reviewing the actual message content.

Wait time

Channel nodes can include a wait setting.

Wait time controls how long 1eyeᴬᴵ waits before moving to the next step.

Examples:

Wait for 0 days
Wait for 1 day
Wait for 3 days

Wait for 0 days
Wait for 1 day
Wait for 3 days

Wait for 0 days
Wait for 1 day
Wait for 3 days

Use wait times to avoid sending too many messages too quickly.

A workflow with wait steps feels more natural and gives target contacts time to respond.

Signal node

A Signal node checks whether a condition happened.

Signal nodes help workflows branch based on target contact or target company activity.

A signal node can create a Yes path and a No path.

Example:

Signal: If LinkedIn accepted
   Yes → Send LinkedIn Message
   No → Send Final Email

Signal: If LinkedIn accepted
   Yes → Send LinkedIn Message
   No → Send Final Email

Signal: If LinkedIn accepted
   Yes → Send LinkedIn Message
   No → Send Final Email

Signal nodes make workflows adaptive.

Signal conditions

Signal conditions may include:

1. If email opened

2. If website visited

3. If ICP

4. If LinkedIn accepted

These conditions let the workflow react to activity and fit.

If email opened

Use If email opened when you want to check whether the target contact opened an email.

Example:

Email: Intro Email
↓
Wait 2 Days
↓
Signal: If email opened
   Yes → Send follow-up email with more context
   No → Send a shorter bump email

Email: Intro Email
↓
Wait 2 Days
↓
Signal: If email opened
   Yes → Send follow-up email with more context
   No → Send a shorter bump email

Email: Intro Email
↓
Wait 2 Days
↓
Signal: If email opened
   Yes → Send follow-up email with more context
   No → Send a shorter bump email

Email opens can be useful, but they are not perfect. Some opens may not be tracked because of email client privacy settings.

Replies are usually more important than opens.

If website visited

Use If website visited when you want to check whether a target contact or company visited your website.

Example:

Email: Intro Email
↓
Wait 3 Days
↓
Signal: If website visited
   Yes → Send high-intent follow-up
   No → Continue normal sequence

Email: Intro Email
↓
Wait 3 Days
↓
Signal: If website visited
   Yes → Send high-intent follow-up
   No → Continue normal sequence

Email: Intro Email
↓
Wait 3 Days
↓
Signal: If website visited
   Yes → Send high-intent follow-up
   No → Continue normal sequence

Website visits can indicate interest, especially when the visit is recent or tied to a high-intent page.

If ICP

Use If ICP when you want to branch based on whether the company matches an ICP from your Knowledge Base.

Example:

Signal: If ICP
   Yes → Send ICP-specific outreach
   No → End or send lower-priority message

Signal: If ICP
   Yes → Send ICP-specific outreach
   No → End or send lower-priority message

Signal: If ICP
   Yes → Send ICP-specific outreach
   No → End or send lower-priority message

This helps keep campaigns focused on target companies that match your strategy.

If LinkedIn accepted

Use If LinkedIn accepted when you want to check whether a LinkedIn connection request was accepted.

Example:

LinkedIn: Connection Request
↓
Wait 1 Day
↓
Signal: If LinkedIn accepted
   Yes → LinkedIn: Send Message
   No → Email: Final Email

LinkedIn: Connection Request
↓
Wait 1 Day
↓
Signal: If LinkedIn accepted
   Yes → LinkedIn: Send Message
   No → Email: Final Email

LinkedIn: Connection Request
↓
Wait 1 Day
↓
Signal: If LinkedIn accepted
   Yes → LinkedIn: Send Message
   No → Email: Final Email

This is useful for multi-channel campaigns where LinkedIn messaging should happen only after the connection is accepted.

Yes and No branches

Signal nodes create two possible paths:

1. Yes
   The condition happened.

2. No
   The condition did not happen.

Use the Yes branch for higher-intent or matching contacts.

Use the No branch for fallback steps, wait steps, different channels, or ending the path.

Example:

Signal: If LinkedIn accepted

Yes path:
LinkedIn: Send Message

No path:
Email: Final Email

Signal: If LinkedIn accepted

Yes path:
LinkedIn: Send Message

No path:
Email: Final Email

Signal: If LinkedIn accepted

Yes path:
LinkedIn: Send Message

No path:
Email: Final Email

Every Yes and No branch should eventually connect to another node or an End node.

Branching best practices

Use branching when different behavior should lead to different next steps.

Good branching examples:

1. If LinkedIn accepted, send LinkedIn message

2. If email opened, send a more specific follow-up

3. If website visited, prioritize the contact

4. If ICP, continue outreach

5. If not ICP, end the sequence

6. If no response, send a final email

Avoid overcomplicating workflows with too many branches before you have enough campaign data.

Message limits

Message limits apply to campaign workflow execution.

Limits can come from:

1. Workspace plan

2. Connected channel limits

3. Mailbox send limits

4. LinkedIn connection limits

5. LinkedIn message limits

6. iMessage new conversation limits

7. User sending schedule

8. Contact-level rules

If a workflow step is not sending, check limits first.

Email limits

Email sends depend on the connected mailbox limit.

The maximum email send limit is:

1,000 emails per day per mailbox

1,000 emails per day per mailbox

1,000 emails per day per mailbox

Your team may choose a lower limit.

Email steps also depend on:

1. Contact has email

2. Contact status is Target

3. Sender mailbox is connected

4. User schedule allows sending

5. Mailbox has remaining capacity

LinkedIn limits

LinkedIn steps depend on connected account limits.

Limits may include:

1. Daily connection requests

2. Weekly connection requests

3. Monthly connection requests

4. Daily messages

5. Weekly messages

6. Monthly messages

LinkedIn steps also depend on:

1. Contact has LinkedIn profile

2. Contact status is Target

3. Sender LinkedIn account is connected

4. User schedule allows sending

5. LinkedIn account has remaining capacity

iMessage limits

iMessage steps depend on the connected iMessage line limit.

Limits may include:

1. New conversations per day

2. Plan-level iMessage line limits

3. Campaign-level controls when available

iMessage steps also depend on:

1. Contact has phone number

2. Contact status is Target

3. iMessage line is Connected

4. Line has remaining capacity

5. Message can be sent as iMessage or SMS fallback

Contact status requirements

Campaign outreach should only run for contacts in Target status.

Before launch, review that target contacts are not:

1. Excluded

2. Archived

3. Converted

4. In the wrong status for campaign outreach

Excluded contacts should not receive outreach.

Workflow save

After changing a workflow, save the workflow.

If the campaign is already running, workflow changes may apply only to future steps.

Always save after:

1. Adding a node

2. Removing a node

3. Editing message content

4. Changing wait time

5. Changing a signal condition

6. Changing branches

7. Changing senders

If you see a warning that the workflow was updated, save to apply the changes.

View Console

The Workflow tab may include a View Console button.

Use Console to inspect campaign execution.

Console helps you see:

1. Executed steps

2. Pending steps

3. Failed steps

4. Which contact is on which node

5. Which node ran

6. When it ran

7. What is scheduled next

8. Message details

Use Console after launch to understand what is actually happening.

Workflow examples

Simple email campaign

Start
↓
Email: Intro Email
↓
Wait 3 Days
↓
Email: Follow-up Email
↓
Wait 3 Days
↓
Email: Final Email
↓
End

Start
↓
Email: Intro Email
↓
Wait 3 Days
↓
Email: Follow-up Email
↓
Wait 3 Days
↓
Email: Final Email
↓
End

Start
↓
Email: Intro Email
↓
Wait 3 Days
↓
Email: Follow-up Email
↓
Wait 3 Days
↓
Email: Final Email
↓
End

Use this when you want a basic email sequence.

Email plus LinkedIn campaign

Start
↓
Email: Intro Email
↓
Wait 1 Day
↓
LinkedIn: Connection Request
↓
Wait 1 Day
↓
Signal: If LinkedIn accepted
   Yes → LinkedIn: Send Message
   No → Email: Final Email
↓
End

Start
↓
Email: Intro Email
↓
Wait 1 Day
↓
LinkedIn: Connection Request
↓
Wait 1 Day
↓
Signal: If LinkedIn accepted
   Yes → LinkedIn: Send Message
   No → Email: Final Email
↓
End

Start
↓
Email: Intro Email
↓
Wait 1 Day
↓
LinkedIn: Connection Request
↓
Wait 1 Day
↓
Signal: If LinkedIn accepted
   Yes → LinkedIn: Send Message
   No → Email: Final Email
↓
End

Use this when LinkedIn should support email outreach.

Signal-based website follow-up

Start
↓
Email: Intro Email
↓
Wait 2 Days
↓
Signal: If website visited
   Yes → Email: High-intent Follow-up
   No → LinkedIn: Connection Request
↓
End

Start
↓
Email: Intro Email
↓
Wait 2 Days
↓
Signal: If website visited
   Yes → Email: High-intent Follow-up
   No → LinkedIn: Connection Request
↓
End

Start
↓
Email: Intro Email
↓
Wait 2 Days
↓
Signal: If website visited
   Yes → Email: High-intent Follow-up
   No → LinkedIn: Connection Request
↓
End

Use this when website activity should change the next step.

ICP-based campaign

Start
↓
Signal: If ICP
   Yes → Email: ICP-specific Intro
   No → End
↓
Wait 2 Days
↓
LinkedIn: Connection Request
↓
End

Start
↓
Signal: If ICP
   Yes → Email: ICP-specific Intro
   No → End
↓
Wait 2 Days
↓
LinkedIn: Connection Request
↓
End

Start
↓
Signal: If ICP
   Yes → Email: ICP-specific Intro
   No → End
↓
Wait 2 Days
↓
LinkedIn: Connection Request
↓
End

Use this when only ICP-fit companies should continue through outreach.

iMessage follow-up campaign

Start
↓
Email: Intro Email
↓
Wait 2 Days
↓
iMessage: Follow-up Message
↓
Wait 2 Days
↓
Email: Final Email
↓
End

Start
↓
Email: Intro Email
↓
Wait 2 Days
↓
iMessage: Follow-up Message
↓
Wait 2 Days
↓
Email: Final Email
↓
End

Start
↓
Email: Intro Email
↓
Wait 2 Days
↓
iMessage: Follow-up Message
↓
Wait 2 Days
↓
Email: Final Email
↓
End

Use this when phone data is available and iMessage is enabled.

Recommended workflow setup

Use this workflow when building a campaign.

1. Open the campaign

2. Go to Workflow

3. Review the Start and End nodes

4. Add the first channel node

5. Select the node type

6. Select the sender

7. Write the message

8. Add wait time

9. Add the next node

10. Add signal conditions if needed

11. Connect Yes and No branches

12. Review every path

13. Save the workflow

14. Preview or launch the campaign

Recommended message setup

Use this workflow when writing messages.

1. Select the message node

2. Choose the message type

3. Choose same message, ICP-specific message, or persona-specific message

4. Select sender

5. Add subject if it is an email

6. Write the body

7. Add variables only where useful

8. Review formatting

9. Test if available

10. Save

Recommended signal setup

Use this workflow when adding a signal condition.

1. Add a Signal node

2. Select the signal condition

3. Connect the previous node into the Signal node

4. Connect the Yes branch

5. Connect the No branch

6. Add wait time before the signal if needed

7. Confirm both branches lead to valid next steps

8. Save the workflow

Best practices

1. Start simple
   Use a clean workflow before building complex branches.

2. Use the right channel for the right step
   Email, LinkedIn, and iMessage should each have a purpose.

3. Select senders early
   Missing senders can block workflow execution.

4. Write messages by ICP or persona when needed
   Better context usually creates better replies.

5. Use wait steps
   Give target contacts time before the next message.

6. Use signal branches intentionally
   Branch only when the next action should actually change.

7. Keep every path connected
   Yes and No branches should not lead nowhere.

8. Make sure every path ends
   Each workflow path should eventually reach an End node.

9. Review limits before launch
   Channel limits affect workflow execution.

10. Use Console after launch
    The Console shows what ran, what is pending, and what failed.

11. Pause before making major changes
    If a running workflow needs major edits, pause and review first.

12. Save after every meaningful change
    Unsaved workflow changes may not apply.

13. Do not over-message
    A thoughtful sequence beats a long, noisy sequence.

14. Respect negative replies and exclusions
    Do not continue outreach to contacts who should not receive messages.

Troubleshooting

I do not see a channel node

Check:

1. Workspace is on a paid plan

2. Channel is enabled in Settings → Engagement Channels

3. Sender account or line is connected

4. Plan includes the channel

5. User has permission

6. Contacts have the required channel data

Email node is not working

Check:

1. Email is enabled

2. Sender mailbox is connected

3. Contact has an email address

4. Contact status is Target

5. Mailbox has remaining send limit

6. User schedule allows sending

7. Email subject and body are complete

LinkedIn node is not working

Check:

1. LinkedIn is enabled

2. Sender LinkedIn account is connected

3. Contact has a LinkedIn profile

4. Contact status is Target

5. LinkedIn account has remaining limits

6. User schedule allows sending

7. The LinkedIn action type is correct

iMessage node is not working

Check:

1. iMessage is enabled

2. iMessage line is Connected

3. Contact has a phone number

4. Contact status is Target

5. Line has remaining daily capacity

6. Message body is complete

7. iMessage or SMS delivery is available

Signal condition is not branching

Check:

1. The correct signal condition is selected

2. There is enough wait time before the signal check

3. The signal actually occurred

4. The Yes branch is connected

5. The No branch is connected

6. The workflow is saved

LinkedIn accepted condition is not working

Check:

1. A LinkedIn connection request step exists before the signal

2. The contact has a LinkedIn profile

3. The LinkedIn account is connected

4. The workflow waits long enough before checking

5. The connection request was actually accepted

6. The Yes and No branches are connected

Website visited condition is not working

Check:

1. Website Signals are active

2. The Vision snippet is installed

3. The contact or company visit is captured

4. The workflow waits long enough before checking

5. The signal condition is saved correctly

Email opened condition is not working

Check:

1. Email was sent

2. Open tracking is available

3. Recipient privacy settings are not blocking tracking

4. The workflow waits long enough before checking

5. The Yes and No branches are connected

Workflow changes are not applying

Check:

1. You saved the workflow

2. The campaign is not paused or ended

3. The change applies to future steps

4. The node is connected correctly

5. Console does not show failed steps

A contact reached the wrong branch

Review:

1. Signal condition

2. Timing

3. Contact activity

4. Available signals

5. Workflow save state

6. Console execution log

Workflow is running but nothing is happening

Check:

1. Campaign status is Running

2. Contacts are in Target status

3. Contacts have required channel data

4. Workflow has connected paths

5. Wait steps are not still pending

6. Channel limits are available

7. Console does not show failures

A node failed

Open Console and inspect the failed node.

Common causes include:

1. Missing sender

2. Missing email

3. Missing LinkedIn profile

4. Missing phone number

5. Disconnected account

6. Channel disabled

7. Send limit reached

8. Contact not in Target status

9. Message content missing

10. Workflow not saved

FAQ

What is a workflow?

A workflow is the sequence of campaign steps that controls messages, channels, wait times, signal checks, branches, and end states.

What channels can workflows use?

Workflows can use Email, LinkedIn, and iMessage when those channels are enabled and connected.

Why do I only see some channel nodes?

Only enabled and connected channels are available.

What does an Email node do?

An Email node sends an email from a connected Google Workspace Gmail mailbox.

What does a LinkedIn node do?

A LinkedIn node sends a LinkedIn connection request or LinkedIn message from a connected LinkedIn account.

What does an iMessage node do?

An iMessage node sends an iMessage from a connected iMessage line. If iMessage is not available for the target contact, the message may be sent as SMS.

Does every node need a sender?

Channel nodes need a sender or line. Email needs a connected mailbox, LinkedIn needs a connected LinkedIn account, and iMessage needs a connected iMessage line.

Does email need a subject?

Yes. Email messages need a subject and body.

Do LinkedIn and iMessage need a subject?

No. LinkedIn and iMessage messages use a message body.

Can I write different messages by ICP?

Yes. Use different messages by ICP when the campaign includes multiple company segments.

Can I write different messages by persona?

Yes. Use different messages by persona when the campaign includes multiple target contact types.

What is a Signal node?

A Signal node checks whether a condition happened and branches the workflow into Yes or No paths.

What signal conditions are available?

Signal conditions may include email opened, website visited, ICP match, and LinkedIn accepted.

What is the Yes branch?

The Yes branch runs when the signal condition is true.

What is the No branch?

The No branch runs when the signal condition is false.

What is Wait For?

Wait For controls how many days 1eyeᴬᴵ waits before moving to the next workflow step.

Do message limits apply to workflows?

Yes. Email, LinkedIn, and iMessage steps are subject to channel, sender, line, plan, and schedule limits.

Do I need to save the workflow?

Yes. Save workflow changes so they apply to the campaign.

Where do I see what happened?

Use Console to view executed, pending, and failed workflow steps.

Next step

Next, go to Console to learn how to monitor campaign execution, inspect node status, and troubleshoot running campaigns.