Copilot Workflows is the intelligent assistant feature in Connectif that allows you to create workflows faster and more easily. Based on the description you provide, Copilot will automatically generate the workflow, including the configuration of its nodes.
This article explains how Copilot Workflows works.
1. Properties
Copilot Workflows enables automatic generation of workflows that respond to the user’s request/description.
Once the user provides the description, Copilot Workflows will generate the workflow with the appropriate strategy for the request made.
- Copilot Workflows can also edit existing workflows by indicating it to the assistant within the same interface.
When creating or editing, the assistant can select existing content to use in content sending nodes.
When creating or editing, the assistant can select existing segments to use in segment nodes and in the initial audience.
- It is possible to generate emails or segments to use in the workflow with Copilot without leaving the workflow editing.
2. How to use it in Connectif
Access Copilot Workflows through the left side menu by clicking on Copilot and then on the Create Workflow option.
Within that menu, you can use the assistant through the initial suggestions you will find in its interface or write your custom request in the area "Describe what you want to create".
You can also access Copilot Workflows through the Workflow creation interface by clicking on Create Workflow and then on Create Workflow with AI.
2.1. Generating a workflow with Copilot
1. In the initial interface of Copilot Workflows, click on Create Workflow.
2. Provide the assistant with the description of the workflow you want to create or choose from the initial suggestions. The more details you provide to Copilot, the closer the flow will be to what you need.
3. The assistant will request, if necessary and within the same chat, additional information to complete the workflow (node configuration and use cases, content types, audiences, etc.).
4. When ready, Copilot will show you the changes directly in the editor. Additionally, it will provide points to consider to optimize your workflow, which you can apply by requesting it directly from the assistant.
5. Review the generated workflow and the configuration of the nodes. Add the content to be displayed in each node (if not already selected) and, if needed, make changes to the node settings.
6. Save and/or activate the workflow.
2.2. Editing workflows with Copilot
1. Within a workflow in Draft status, click on the Copilot Workflow option.
2. Request the modifications you want to make from the assistant. These include:
- Adding or removing branches and nodes.
- Editing the configuration of the nodes.
- Explaining a workflow.
- Adding annotations.
3. Review these changes and, once ready, save or activate the workflow.
2.3. Reviewing the generated workflow
Once the workflow is generated, Copilot will indicate if it is ready for activation or if additional configurations are required on some nodes:
2.3.1. The workflow is ready
All nodes will be configured and the workflow can be activated. A confirmation message will be displayed.
It is recommended to review the generated content before activation to ensure it fits the strategy’s needs.
2.3.2. Some nodes require your attention
Copilot will indicate which nodes require manual configuration and the necessary actions to complete them. For example: Select your email content in the Send Email node or The segment "Loyal Buyers" was not found automatically. Create it first or verify the name.
In these cases, it is possible to:
- Tell Copilot the desired action so it can perform the configuration automatically.
- Access the node from the editor and complete the configuration manually.
2.4. Prompt guide
This section details recommendations for writing requests to Copilot to obtain more precise workflows tailored to each strategy’s needs.
2.4.1. Best practices for creating a workflow
The more context you provide, the more complete the workflow generated from the start will be. For this, it is recommended to provide Copilot with the following information:
- Objective: indicate the business outcome you want to achieve. For example: recover abandoned carts, welcome new subscribers, reactivate inactive users, or sell more on Black Friday.
-
Channel: indicate the communication channel. If not specified, Copilot may request this information.
For example: email, SMS, push notifications, web content (popup, inline). - Execution time (optional): indicate when the actions should be executed. For example: send 1 hour after the event, every Monday at 9am, or 3 days after registration.
- Conditions (optional): indicate filters or rules that determine which contacts will receive the action. For example: only if the cart exceeds €50, only for subscribers who haven’t opened an email in 90 days, or only for users in the VIP segment.
Copilot automatically generates the workflow structure based on the objective, configures audience restrictions according to the channel, identifies existing segments and content by their name, and applies default values for timing and execution. Additionally, it assigns a name and description to the workflow and uses sector information and store description if configured.
For better results, it is recommended to provide clear and direct descriptions, including context when relevant. It is not necessary to specify technical details, as Copilot manages these automatically. Only one workflow is generated per request, which can be adjusted later if needed.
2.4.2. Examples of prompts to edit workflows
Below are some example requests that can be used to modify workflows via Copilot:
Change the wait time to 2 hours.
Add a condition: only continue if the cart exceeds €50.
Replace the email node with an SMS node.
Add an A/B test that splits traffic 50/50 between two subject lines.
Remove the second timer.
Direct only to contacts in the "VIP Clients" segment.
Use the email "Summer Campaign" in the email sending step.
Send the email on Mondays at 9am instead of 10am.
To refer to a node, it is necessary to use its identifier with the syntax @id. For example: delete node @12.
2.4.3. Elements to add to improve prompts
It is recommended to use a clear structure in the request to Copilot to improve the accuracy of workflows generated by Copilot. To do this, make sure to:
- Define the objective and channel. For example: Create a reactivation workflow for users who haven’t opened any email in the last 90 days. Use the email channel.
- Indicate content, sending time, and conditions. For example: Create a post-purchase follow-up. Send the email 'Thank you for your purchase' 2 days after a purchase is completed, only for new buyers.
- Configure scheduled workflows with defined channel, content, and timing. For example: Every Friday at 5pm, send a push notification "Weekend News" to all push subscribers.
- Reference segments by their name. For example: Send the email only to users in the "High Value Clients" segment.
Copilot will automatically identify existing segments and content based on the names provided.
2.4.4. Actions that can cause inefficiencies in prompts
It is recommended to avoid ambiguous or incomplete requests and always provide the necessary information. To do this, avoid:
- Requesting a workflow without an objective or context. For example: Help me with marketing. Copilot requires an objective and channel to generate a useful workflow. Use a prompt like: Create a workflow that sends a loyalty email for recurring customers.
- Requesting multiple workflows. For example: Create two workflows at once. Copilot only generates one workflow per request. Generate each workflow separately using one prompt at a time. For example: Create a cart recovery workflow and Create a welcome series for new subscribers.
- Requesting a workflow without defining a clear outcome. For example: Build a workflow from scratch with no basis. Copilot needs a concrete objective to generate the workflow.
2.5. Final recommendations
Following a series of best practices when writing requests to Copilot will allow you to obtain more precise results when creating or editing workflows.
2.5.1. Recommendations:
Clearly describe the objective and channel.
Reference segments and content by their name so Copilot can identify them automatically.
Include timing information when relevant. For example: Send after 1 hour, every Monday.
Add conditions from the start of the request. For example: Only carts > €50.
Make editing requests one at a time to improve accuracy.
Request Copilot to configure pending nodes after generating the workflow.
Reference nodes by their identifier using the syntax "@id".
2.5.2 Actions to avoid:
Requesting more than one workflow in the same request.
Including technical identifiers, as Copilot manages these automatically.
Requesting content writing or copywriting. Trying to modify workflows that are not open in the editor.
Using ambiguous requests without specifying the desired change. For example: improve it.
Requesting automatic scheduling or activation of workflows.
Congratulations!
You have reached the end of the lesson.
Do you still have unresolved questions?
Remember that our specialists at Connectif are available to assist you. To contact them, just open a support ticket by clicking on the blue “Help” button on your dashboard.
Keep learning!
To take full advantage of your Connectif account’s potential, we recommend continuing with the following articles:
Connectif Copilot, to learn about the assistant’s functionality and interface.
Creating emails with Copilot, to learn how to use the assistant to quickly create emails.
Viewing statistics and data in Connectif, to learn in which other areas of Connectif you can see your eCommerce’s performance and your contacts’ activity.
Data Explorer, to learn how to create your own reports and export them easily.