This release expands the Content Agent chat functionality (contextual chat) to the email, landing page, and SoMe post builders.
You can now drag and drop tiles directly into the chat of any element — giving you full context for what you’re writing and allowing Magnity to understand the intent and background of your content.
💬 Chat Functionality in All Builders
The same intuitive chat experience from the Content Agent is now available across all builders.
When editing an email, landing page, or SoMe post, you can:
This makes it easy to continue work, refine outputs, and reuse existing content without searching for tiles again.

📚 Why It Matters
Adding context directly in the builder unlocks a new level of precision and speed.
Since you can build tiles in the Content Agent, you can now use virtually any type of tile as context when writing:
You can even reapply a specific source to refocus Magnity’s attention.
For example, if you’ve added a Flow Plan and want to discuss how one page has been implemented, you no longer need to locate the tile again — simply reapply it from the list of previously used tiles.
This gives users the flexibility to test, adjust, and iterate content with precision — all within the builder environment.
🖼️ Image Hosting Options: Now Available for Pardot (Salesforce Marketing Cloud Account Engagement)
Following last month’s update, where you could choose to host images either on Magnity’s Bytescale CDN or send them directly to Marketo, the same functionality is now also available for Pardot (Salesforce Marketing Cloud Account Engagement).
This gives you the same flexibility when working with Pardot campaigns ensuring consistent link tracking and full compatibility when sending emails to recipients in organizations with strict email security configurations.
By aligning image hosting with your platform domain, this feature helps maintain consistent link tracking and minimizes link adaptations caused by differing domains.
🧩 Minor Improvements
Fixed a few minor issues:
🔍 Known Issues
When requesting very large output texts (for example, long rewrites or translations), the interface may become unresponsive if the chat reaches its output token limit.
We’re working on a fix that will allow large outputs to be handled in multiple stitched responses.
Until then, try splitting large tasks into smaller chunks if you experience a timeout.
🎯 Why This Matters
This release is a step toward making Magnity fully context-aware across all content types.
By extending the Content Agent’s chat capabilities to every builder, you can now create smarter, faster, and more connected content experiences — powered by the same reasoning layer used in the Content Agent.
It also marks an important milestone toward the Journey Agent, a system that will automatically build complete automation flows from your existing content, combining reasoning, sequencing, and personalization.
We’re excited to move closer to that goal with this release.
Questions or Feedback?
Our support team is here to help:
✉️ ulsa@magnity.ai | 📞 +45 29 35 25 78
Thank you for using Magnity!
— The Magnity Development Team