Custom action limitations

Custom actions extend what Marketing agent can build, but they work within specific boundaries. See Marketing agent limitations for limits that apply to the agent as a whole. For what custom actions are, see Custom actions.

Building custom actions

• Built in Marketing agent only: You create and change custom actions through conversation with Marketing agent. You can see a Custom action node in the scenario editor, but you can't open or edit its logic there.
• Used only when needed: Marketing agent adds a custom action only when standard scenario features can't do the job. You can't force it to use one for logic that standard features already cover.
• One campaign at a time: A custom action belongs to the campaign it was built for.
• Channels: Custom actions work in campaigns on the channels Marketing agent supports. See Agent capabilities.

Data and integrations

• External data needs an existing integration: Custom actions can only call external systems that are already connected as integrations in Marketing. Marketing agent can't create a new integration for you.
• Integration timeouts and limits: Calls to external systems follow the standard timeouts and limits that apply to any integration. See Webhooks integration setup.
• No credentials in prompts: You can't add API keys, tokens, or passwords to a custom action through the conversation. Credentials must be stored in the integration.
• Per-recipient logic: A custom action runs separately for each customer and only sees that customer's data, it can't compare customers with each other. For example, it can't rank all customers by spend and pick the top 10,000. Use a segmentation or aggregate for logic across your whole audience.
• Writing data back: A custom action prepares data but doesn't save it by itself. To store a result on the customer profile or as an event, Marketing agent adds a separate node after the custom action.

Preview and testing

• Previews don't run custom actions: Email previews and test emails skip the custom action, so they don't show the personalized result each customer will get. Use a test run to see real output. See Test and troubleshoot custom actions.
• Explanations aren't test results: When Marketing agent explains what a custom action does for a particular customer, it describes how the logic should behave. It doesn't run the logic against live data. Confirm with a test run.
• Preview errors: In some cases, a scenario with a custom action may not render a preview. This doesn't affect how the scenario runs.

Reporting and monitoring

• What's recorded: Sends and message content are tracked as usual, subject to your project's storage settings. The custom action's inputs, its results, and any data it sends to an external system aren't recorded. If you need them (for example, to check why a customer went down a branch, or to keep an audit trail of data sent to a partner) ask Marketing agent to save them as an event or customer property when you build the campaign.
• Live campaigns: Changes to a custom action in a live campaign take effect only after you republish the campaign.