- Product documentation
- Latest Updates
- Release Notes
- Getting started
- Profiles and audiences
- Communication channels
- Designing email content
- Testing and Sending
- Reporting
- Integrating with other solutions
- Managing processes and data
- Get started with data and processes management
- Workflow general operation
- Executing a workflow
- Calling a workflow with external parameters
- Targeting activities
- Execution activities
- Channel activities
- Data management activities
- Filtering data
- Importing and exporting data
- Use cases
- About workflow use cases
- Deliveries
- Creating deliveries with a complement
- Creating deliveries on profiles’ creation date
- Creating a weekly delivery
- Creating a cross-channel delivery
- Identifying duplicates before a delivery
- Birthday delivery
- Coupling email and direct mail deliveries
- Sending an email with enriched fields
- Personalizing an email with additional data
- Sending a recurring push notification
- Segmentation and targeting
- Data management
- Reconcile a File audience with the database
- Deduplicating the data from an imported file
- Enriching profile data with data contained in a file
- External signal activity and data import
- Updating the database with external data
- Updating data based on an automatic file download
- Data reconciliation using relations
- Data update using reconciliation
- Exporting profiles in an external file
- Updating multiple subscription statuses from a file
- Subscribing profiles from a file to a specific service
- Working with Adobe Experience Platform audiences
- Developing
- Administrating
- Get started with Campaign Standard administration
- Monitoring guidelines
- Configuration guidelines
- Users and security
- Configuring channels
- Configuring mobile channels
- Implementing Push tracking
- Adding images and videos iOS
- Understanding push notifications payload structure
- Implementing local notification tracking
- Adobe Launch Synchronization FAQ
- Experience Platform SDK integration FAQ
- Configuring Launch rules to support Adobe Campaign Standard use cases
- Mobile use cases supported in Adobe Campaign Standard
- Application settings
- Working with APIs
- Get started with Campaign Standard APIs
- About Campaign Standard APIs
- Global concepts
- Interacting with custom resources
- Managing profiles
- Managing services and subscriptions
- Interacting with marketing history
- Privacy management
- Managing transactional messages
- Managing workflows
- Managing organizational units
- Managing geographical units
- Troubleshooting
Overview
Campaign Standard lets you call a workflow with parameters (an audience name to target, a file name to import, a part of message content, etc.). This way, you can easily integrate your Campaign automations with your external system.
Let’s take the following example, where we want to send emails directly from a CMS. In that case, you can configure your system to select the audience and email content into the CMS. Clicking on Send will then call a Campaign workflow with these parameters, enabling you to use them into the workflow to define the audience and URL content to use in the delivery.
The process to call a workflow with parameters is the following:
- Declare the parameters in the External signal activity. See Declaring the parameters in the External signal activity.
- Configure the End activity or the API call to define the parameters and trigger the workflow External signal activity. See this page
- Once the workflow has been triggered, the parameters are ingested into the workflow’s events variables and can be used within the workflow. See this page.
