Maintain Your MuleSoft Hyperautomation Developer Certification for Winter '26

Learning Objectives

After completing this unit, you’ll be able to:

Create Generic document actions in MuleSoft Intelligent Document Processing (IDP) with custom schemas.
Secure documents in IDP with PII masking, signature detection, and Base64 uploads.
Authenticate MuleSoft API connections with Basic, JWT, or OAuth 2.0.
Manage API Catalog entities across orgs and set connections per Flow action.
Build Flow integrations with new connectors and templates.
Trigger flows from external systems with polling and conditional triggers.
Transform Flow data with the Transform Input Configurator, collection values, and filters.

Stay Current with Your Certification

Salesforce certifications hold the most value when you keep them relevant. To keep your MuleSoft Hyperautomation Developer certification current, complete this module by the due date.

Interested in learning more about getting certified? Check out the MuleSoft Hyperautomation Developer certification.

While anyone can earn this badge, this module is designed for those who hold the MuleSoft Hyperautomation Developer certification.

As part of the Salesforce Certification Program, you agree to the terms of the Salesforce Certification Program Agreement. Review the exam policies in the agreement and the Salesforce Certification Program Agreement and Code of Conduct article before you continue.

MuleSoft Hyperautomation Developer Certification Overview

Hyperautomation combines AI, machine learning, robotic process automation (RPA), and low- or no-code tools to automate business and IT processes at scale. You use these capabilities to modernize legacy systems, connect applications, and create smarter workflows.

As a MuleSoft Hyperautomation Developer, you deliver value when you:

Design and deliver automation solutions that connect Salesforce, MuleSoft, and external systems.
Spot automation opportunities and select the right tools to address them.
Measure the impact of automation on business goals.
Bridge business and IT through shared tools and integrated processes.

You also work with key components, including:

Anypoint Platform for designing, building, and managing APIs and integrations at scale.
Composer for creating no-code integrations and workflows.
Robotic process automation (RPA) for automating manual, repetitive tasks with bots.
Intelligent document processing (IDP) for extracting and transforming document data with AI.
Salesforce Flow and Flow Orchestration for building and coordinating multi-step processes.
Anypoint Exchange for discovering, sharing, and reusing integration assets.

Salesforce released new features this year that help you deliver even more powerful hyperautomation solutions. In this module, we explore the most important updates.

What’s New for MuleSoft Intelligent Document Processing

Most every organization works with documents: invoices, contracts, receipts, human resources files, and many more. Most of these documents aren’t neatly structured, which makes them hard to process automatically.

With MuleSoft Intelligent Document Processing (IDP), developers use AI-powered tools to extract and transform this information. The newest features expand how developers capture, secure, and manage document data in their workflows.

With these updates, developers:

Design custom schemas with Generic document actions. Create a Generic document action and enable Customize Schema to define exactly which output fields to capture using natural language prompts, including non-English characters when needed.
Work with images as well as text. Use image recognition to pull details from scanned or photographed files, like receipts with logos, totals, or signatures.
Choose from more models. Run document actions with GPT-4o, GPT-4o Mini, or Google Gemini 2.0 Flash 001 for flexibility to balance speed, accuracy, and cost.
Add longer instructions. Supply up to 128,000 tokens in Einstein prompts to guide how the model interprets complex or multipage documents.
Protect sensitive information. Mask personally identifiable information (PII) before sending content to a predictive model, and detect signatures for added security checks.
Handle new formats. Upload files in Base64 encoding for versioned action executions, which makes it easier to support different systems.
Rely on clear retention policies. Know that successful runs are stored for 24 hours and incomplete tasks for 30 days—important for both auditability and compliance.

Imagine a developer automating vendor invoice processing. Some invoices arrive as clean PDFs, others as photos taken on a phone. The developer creates a custom schema with fields for vendor ID, invoice amount, and due date. Image recognition ensures even a slightly blurry photo yields usable totals. When handling contracts, the developer applies PII masking to keep employee details private, while signature detection verifies that scanned agreements are complete. If the process fails halfway through, they know the task data will remain available for 30 days to troubleshoot.

Together, these features give developers more control, more security, and more flexibility in how they use IDP, turning unstructured documents into reliable data their organizations can use.

Tip

Use Base64 encoding when automating uploads to keep large, complex files consistent across environments.

Recent Enhancements to the MuleSoft API Catalog

With API Catalog, developers bring APIs into Salesforce so teams can find them, secure them, and use their actions in agents, Apex, and flows. After connecting a Salesforce org to Anypoint Platform, developers sync APIs with the catalog, create per-version connections, assign permissions, and activate actions. Builders then select connections directly in Flow.

Recent updates give developers more flexibility and control to:

Use more authentication methods. Create connections with Basic, JWT, or OAuth 2.0 authentication protocols, in addition to client ID enforcement, and configure External Credentials to keep access secure.
Package and promote across orgs. Move catalog data with first- or second-generation managed packages so sandboxes and production stay aligned. Key entities include Named Credentials, External Credentials, and permission sets, which means teams don’t have to rebuild configurations manually.
Select a connection per action in Flow. In Flow Builder, pick which API connection an action should use. This makes it easy to switch between sandbox, production, or region-specific environments without duplicating flows.
Manage multiple connections per API version. Keep separate connections for different backends (for example, US vs. EU) and set one as the default so actions always point to the right target.
Keep catalogs clean and accurate. Sort and filter lists for easier discovery, remove unused APIs or versions, and check permission status so flows don’t fail at runtime. When removing a MuleSoft API, first deactivate its actions in flows and agents, then remove the sf-api-catalog tag in Anypoint Exchange to prevent the API from syncing back in.
Broaden sources when needed. Surface Heroku APIs directly in the catalog, and experiment with the beta option to show Apex endpoints—including AuraEnabled controller methods—as actions.

With all of these enhancements, developers secure APIs with the correct authentication methods, manage connections across multiple environments, package and promote catalog data to keep orgs consistent and up to date. The result is simpler management of APIs across orgs and greater confidence that actions run in the intended flows.

Tip

If a connection looks fine but actions fail at runtime, check permission status in API Catalog and re-assign users to the generated permission set.

Removing a MuleSoft API from Catalog? Deactivate its actions in flows/agents first. If it’s a MuleSoft API that keeps reappearing after sync, remove the sf-api-catalog tag in Anypoint Exchange to prevent it from coming back.

Key Updates in MuleSoft for Flow: Integration

MuleSoft for Flow: Integration gives developers and admins no-code ways to connect Salesforce flows with external systems. By adding third-party connectors as triggers or actions, teams exchange data across platforms without custom code. The Connections and Integrations tabs in the Automation app make it easier to manage, monitor, and reuse these links.

Here are the key updates that expand what developers can do with Flow integrations.

Work with more connectors. Add Gmail, Microsoft Teams, Zoom, and many other third-party connectors to flows. Use them as triggers (for example, when a meeting is scheduled) or as actions (such as sending an email or updating a record).
Trigger flows from external events. Use the External System Change-Triggered flow type to start automations when data changes in connected systems like NetSuite or Jira.
Poll more frequently with conditional triggers. Adjust how often flows check external systems, and use conditional triggers to run them only when certain fields change—reducing unnecessary API calls.
Manage integrations in one place. Use the Integrations tab to view, create, edit, or delete connections, check usage, and test validity when loading flows. This helps prevent broken automations before they happen.
Map data more easily. Use the Transform Input Configurator or in-line mapping tools to shape data between systems. Define collection field values directly in a flow, or retrieve external records with filters and limits that match Flow Builder’s Get Records style.
Handle input values more efficiently. Use static or dynamic providers, see labels instead of raw values, and include custom fields from systems like Jira or QuickBooks.
Accelerate flow setup. Start with integration templates such as Salesforce-to-Salesforce case replication or OpenAI case urgency classification. Templates provide a guided configuration experience and best practices for common use cases.

These improvements give developers practical ways to build stronger integrations: pulling only the records they need, running flows when changes actually matter, keeping connections up to date, and starting faster with templates. The result is more reliable data exchange and less manual maintenance across systems.

Minor and patch connector updates install automatically, but major versions require a manual upgrade. This keeps integrations secure while giving you control over breaking changes.

Wrap-Up

Here’s what you covered in this unit.

MuleSoft IDP adds new ways to shape outputs, work with images, choose models, and protect sensitive data.
API Catalog offers more authentication options, packaging tools, and easier ways to manage connections.
MuleSoft for Flow: Integration includes more connectors, smarter triggers, better data handling, and quick-start templates.

With these updates, you’re ready to maintain your MuleSoft Hyperautomation Developer certification and keep building automations that are faster, smarter, and easier to manage.

时间估计

主题

需要帮助？

MuleSoft 资源