![]() To ensure the flow works as intended, you can test it in Composer by providing sample values for your inputs. If invoking the Composer flow from Flow Builder, once you receive the status back from Composer, you can build your automation further to take the appropriate action based on the order status. In V2, the order status can be returned back to the caller. In the Service Cloud use case above, let’s define a flow in Composer that takes two inputs: orderId and channelName. We’ll build the flow in Composer such that the Composer flow retrieves the status of the order from NetSuite (using the orderID) and sends a message to the fulfillment team via a Slack channel (specified by channelName). Inputs can be specified using the Visual Editor (supports primitives such as String, Number, Boolean, Date, and Datetime) or via the Sample JSON Editor (supports complex inputs such as arrays, objects, and lists). ![]() We’ll begin by building a flow in Composer using the newly introduced trigger called Invoke.įlows that use the Invoke trigger can be invoked from external systems and can receive inputs (V1) and return outputs (V2). ![]() And we wish to build this automation all within Salesforce! We then want to use the order status to update the fulfillment team using Slack. We want to use the custom record ID coming from Service Cloud to retrieve the corresponding order status from NetSuite. In the example shown below, we have a Service Cloud customer enquiring about their order status using an Einstein Bot. In the case of Flow Builder, the Composer flow will be able to return values to the flow that invoked it. The V2 release (slated for later in FY24) will allow Composer flows to return outputs back to the caller. Coming in July 2023, the V1 release will allow Invocable Composer Flows to accept inputs and build automations using the values passed in. Invocable Composer Flows will become Generally Available (GA) in two phases. How do you configure a Composer flow to be invoked?Ĭomposer users will be able to configure their Composer flow so that it receives custom inputs from wherever it’s invoked and can also return outputs in response. Build powerful automations by leveraging the built-in support for input and output parameters.Create application programming interface (API)-compatible invocable actions for seamless integration with diverse systems and applications.Authenticate every invocation for a secure and protected automation experience.Automate end-to-end across Salesforce by calling Composer flows directly from Flow Builder.Here are a few highlights of what’s possible with Invocable Composer Flows. Using Invocable Composer Flows, you can now build this integration in Flow Builder without writing a single line of code! With Invocable Composer Flows, you can now connect to third-party systems such as NetSuite, JIRA, and Workday from Flow Builder with just a few clicks! Here’s an example: Let’s say you want a JIRA issue to be generated and a Slack message to be sent to the sales team as soon as a new record (contact, lead, opportunity, etc.) is created in Salesforce. This feature allows users to call Composer flows from Flow Builder (and later from Flow Orchestration). To further supercharge the integration capabilities of Composer, we’re introducing Invocable Composer Flows. It’s a no-code tool you can use to build automations with only clicks. Using Composer, you can quickly and easily build flows to integrate systems and data and automate integration tasks. MuleSoft Composer is an integration tool designed for admins, business analysts, marketers, salespeople, and team leaders.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |