A number of the materials (posts, tutorials, etc.) available out there present an approach to integration between MuleSoft and Salesforce on the basis that MuleSoft is always proactively responsible for starting communication, injecting or pulling CRM data based on a schedule or otherwise.
This post aims to present a different approach to integration between these two platforms, where MuleSoft works in a more reactive way, triggered by notifications (events) sent by Salesforce representing new or modified data,
Alexandra Martinez is a member of our Developer Community and has been leading our Meetup Group in Toronto for a few years now. She brings her local community together on a regular cadence, each time with more and more attendees. For more information on how to join the MuleSoft Community, visit our Community page.
Before this app, our HR department at Bits In Glass (BIG) was manually posting messages to different Slack channels in our workspace.
Apache Kafka is used for building real-time data pipelines and streaming apps. It is horizontally scalable, fault-tolerant, and incredibly fast. And when coupled with Heroku and MuleSoft, developers can easily publish and consume data without writing any code.
In this article, we’ll walk-through the process of configuring the MuleSoft Kafka connector to connect to Apache Kafka on Heroku through SSL. Using the MuleSoft Kafka Connector, developers can streamline business processes and move data between Kafka and enterprise applications and services.
If you have worked with Mule for any period of time you know that we provide deep support for interacting with Salesforce Clouds – including connectors, templates, and examples. But you may not be aware that Salesforce exposes many different APIs that our connectors leverage for these integrations. Many developers may be familiar with the real-time, bulk, or streaming integration patterns that Salesforce supports. This blog will touch on a lesser-known API resource Salesforce has released and the MuleSoft connector that supports it.
SAP’s flagship on-premise ERP, known as ERP Central Component (ECC), is quickly approaching its end of maintenance in 2027. As a result, customers are beginning to migrate their applications, processes, and data to SAP’s next-generation solution, SAP S/4HANA Cloud.
Are you stuck with business as usual where you end up building solutions with a platform as a service (PaaS) for project needs? Do you want to get out of always being reactive, creating further technical debt and never able to execute the vision of building rapid solutions that would end up being assets to your organization? This is my story of how I reduced IT costs and the increased project quality at a large beverage company.
Regardless of how customized your SAP instance(s) may be, or how mismatched the object models may be between SAP and third-party solutions, Anypoint Platform is purpose-built to abstract the complexity of any system and its proprietary language. This results in obviating the need to build with custom code by leveraging an API-led approach.
In the digital economy, connectivity is everything. A key part of connectivity is growing an ecosystem that enables you to tap into data from anywhere.
At MuleSoft, we enable connectivity to everything. As a No. 1 priority, we will continue to invest in tooling that makes it easy to build your own connectors as well as connect to any API. As such, we are constantly expanding and updating the number of connectors provided by MuleSoft and our ecosystem.
MuleSoft provides the most widely used integration platform for connecting any application, data source or API, whether in the cloud or on-premises. With Anypoint Platform®, MuleSoft delivers a complete integration experience built on proven open source technology, eliminating the pain and cost of point-to-point integration. Anypoint Platform includes CloudHub™ iPaaS, Mule ESB™, and a unified solution for API management™, design and publishing.