# mulesoft Composer - Full Documentation --- product: Composer --- # Connector Reference > For the full documentation index, see: https://docs.mulesoft.com/llms.txt > [!NOTE] This is a test note. ## Connections To connect to a system, whether it is a source of data or the target where you are sending data, you must create a connection with that system’s required credentials. You typically connect to different systems within a flow and can reuse each connection every time you need to connect. This system requires the following credential information for its connections: Connection Name Enter a connection name that will help you remember the details of this connection. You can reuse connections multiple times in a single flow, and in more than one flow, and the credentials are hidden after you create the connection. Therefore, it’s helpful to provide a name that easily identifies this connection from others. Only you can see the connection. Other users in your Composer app must create their own connections. Username The username that you use to log in to . Password The password that you use to log in to .

. ## Triggers Each flow starts with either a _scheduler_ or a _trigger_. Schedulers are set to a default frequency of 15 minutes. Triggers, such as "each time a new record is created", are defined by you and provide multiple options related to the data in your system. Triggers use a polling process to actively check for new updates from an external system. The polling frequency is 15 seconds. This system provides the following trigger options:

. ## Actions After you connect to a system and define the trigger or configure a scheduler, you define the actions that the flow performs. For example, you can copy a record between different systems, such as Workday and Salesforce. The actions you can perform depend on which system you are connected to. This system provides the following actions:

. ## Objects

. ## See Also - [Mulesoft Composer: Overview](https://docs.mulesoft.com/composer/ms_composer_overview) - [MuleSoft Composer: Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) - [Composer Connector Reference](https://docs.mulesoft.com/composer/ms_composer_reference) - [Knowledge Articles](https://help.salesforce.com/s/) --- product: Composer --- # Activating a Composer Flow > For the full documentation index, see: https://docs.mulesoft.com/llms.txt After you [build](https://docs.mulesoft.com/composer/ms_composer_using_a_flow_and_creating_trigger#create-a-new-flow) and [test](https://docs.mulesoft.com/composer/ms_composer_test_flow) a flow in a sandbox environment, [connect](https://docs.mulesoft.com/composer/ms_composer_connecting_a_flow) your flow to a production environment. After testing your flow in the production environment, you can activate it. To activate your flow: 1. In Composer, find the flow you want to activate in the flows list. Your flow status is listed as **Inactive**. 2. Click the flow name to open it. 3. Click **Edit**. 4. Click **Activate**. Composer notifies you when the flow is activated. ## See Also - [Mulesoft Composer: Overview](https://docs.mulesoft.com/composer/ms_composer_overview) - [MuleSoft Composer: Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) - [Composer Connector Reference](https://docs.mulesoft.com/composer/ms_composer_reference) - [Knowledge Articles](https://help.salesforce.com/s/) --- product: Composer --- # Asana Connector Reference > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Asana is a SaaS-based project management tool that enables teams of all sizes to manage their daily tasks, schedules, and deliverables. ## Connections To connect to a system, whether it is a source of data or the target where you are sending data, you must create a connection with that system’s required credentials. You typically connect to different systems within a flow and can reuse each connection every time you need to connect. This system requires the following credential information for its connections: Connection Name Enter a connection name that will help you remember the details of this connection. You can reuse connections multiple times in a single flow, and in more than one flow, and the credentials are hidden after you create the connection. Therefore, it’s helpful to provide a name that easily identifies this connection from others. Only you can see the connection. Other users in your Composer app must create their own connections. Older connections may expire if not regularly used. Asana sets the amount of time a connection remains valid. Username The OAuth username that you use to log in to Asana. Password The OAuth password that you use to log into Asana. ## Triggers Each flow starts with either a _scheduler_ or a _trigger_. Schedulers are set to a default frequency of 15 minutes. Triggers, such as "each time a new record is created", are defined by you and provide multiple options related to the data in your system. Triggers use a polling process to actively check for new updates from an external system. The polling frequency is 15 seconds. This system provides the following trigger options: New or updated task Fires when a task is created or an existing task is updated. ### Polling Frequency For triggers in this connector, the **Polling Frequency** field is required. This field enables you to select how often Composer makes a request to the underling system API to look for changes to records in active flows. You can select a different polling frequency for each flow in your organization. With a shorter frequency, the flow executes more often; however, a shorter frequency consumes more [API calls](https://docs.mulesoft.com/general/automation-credits-usage-and-rates). For example, if you have an order management flow, you might require nearly real-time updates, which can be achieved with a 15-second polling interval (which equates to 5760 API calls per day). In contrast, if your flow updates a pricing catalog, you could poll the flow every hour (which equates to 24 API calls per day). ## Actions After you connect to a system and define the trigger or configure a scheduler, you define the actions that the flow performs. For example, you can copy a record between different systems, such as Workday and Salesforce. The actions you can perform depend on which system you are connected to. This system provides the following actions: Create new task Creates a new task record. When creating a new task record, store the values for both the User ID and the Task ID in the source system for use when updating task records. Update task Returns the completed and updated task record. Add comment to card Comment on a task to ask questions, provide extra information, or to offer insight. The comment appears on the card. ## Custom Fields Custom fields are not supported. Using MuleSoft Composer, you can access standard field values for actions and triggers that you set in the Asana record. ## See Also - [Mulesoft Composer: Overview](https://docs.mulesoft.com/composer/ms_composer_overview) - [MuleSoft Composer: Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) - [Composer Connector Reference](https://docs.mulesoft.com/composer/ms_composer_reference) - [Knowledge Articles](https://help.salesforce.com/s/) --- product: Composer --- # Box Connector Reference > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Box is a general purpose, SaaS enterprise content management system. Organizations use Box to securely manage and to collaborate on documents, images, videos and various other files. ## Connections To connect to a system, whether it is a source of data or the target where you are sending data, you must create a connection with that system’s required credentials. You typically connect to different systems within a flow and can reuse each connection every time you need to connect. This system requires the following credential information for its connections: Connection Name Enter a connection name that will help you remember the details of this connection. You can reuse connections multiple times in a single flow, and in more than one flow, and the credentials are hidden after you create the connection. Therefore, it’s helpful to provide a name that easily identifies this connection from others. Only you can see the connection. Other users in your Composer app must create their own connections. Username The OAuth username that you use to log in to Box. Password The OAuth password that you use to log in to Box. ## Transfer Binary Files You can transfer binary files as field inputs using data pills from within your Composer flow. For example, when keeping files in sync between Box instances, you can download binary file content from one instance and later upload that same file content to another instance. The recommended file size limit per transfer is 25MB and files transferred across systems cannot be truncated. ## Triggers Each flow starts with either a _scheduler_ or a _trigger_. Schedulers are set to a default frequency of 15 minutes. Triggers, such as "each time a new record is created", are defined by you and provide multiple options related to the data in your system. Triggers use a polling process to actively check for new updates from an external system. The polling frequency is 15 seconds. This system provides the following trigger options: On new file in folder Triggers when a new folder is added. Provide a value for **Folder ID**. ### Polling Frequency For triggers in this connector, the **Polling Frequency** field is required. This field enables you to select how often Composer makes a request to the underling system API to look for changes to records in active flows. You can select a different polling frequency for each flow in your organization. With a shorter frequency, the flow executes more often; however, a shorter frequency consumes more [API calls](https://docs.mulesoft.com/general/automation-credits-usage-and-rates). For example, if you have an order management flow, you might require nearly real-time updates, which can be achieved with a 15-second polling interval (which equates to 5760 API calls per day). In contrast, if your flow updates a pricing catalog, you could poll the flow every hour (which equates to 24 API calls per day). ## Actions After you connect to a system and define the trigger or configure a scheduler, you define the actions that the flow performs. For example, you can copy a record between different systems, such as Workday and Salesforce. The actions you can perform depend on which system you are connected to. This system provides the following actions: Add file to folder using URL Adds a file to a folder in Box which is referenced by a publicly-shared URL. Provide a value for the following fields: - **Folder ID** - **Source URL** Upload File Adds a file to a folder in Box. Provide a value for the following fields: - **File Name** - **File contents** - **Folder ID** - **Existing File ID** Download File Returns the binary contents of the specified file and version. Provide a value for the following fields: - **File ID** - **Version** Create folder Creates a folder in the Box structure. Provide a value for the following fields: - **Parent Folder ID** - **Folder name** Create file metadata Creates file metadata by populating a metadata template on a file in Box. Provide a value for the following fields: - **File ID** - **Metadata template** Multiple selection field types, such as checkboxes, do not appear in Composer. Update file metadata Updates file metadata by updating the existing metadata template on a file in Box. Provide a value for the following fields: - **File ID** - **Metadata template** Multiple selection field types, such as checkboxes, do not appear in Composer. ## See Also - [Mulesoft Composer: Overview](https://docs.mulesoft.com/composer/ms_composer_overview) - [MuleSoft Composer: Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) - [Composer Connector Reference](https://docs.mulesoft.com/composer/ms_composer_reference) - [Knowledge Articles](https://help.salesforce.com/s/) --- product: Composer --- # Building a Flow Using Templates > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You can create a new flow from a template. Templates are patterns that you can leverage to build a flow. All of the steps and field mappings are predefined, so you can select the template and enter the missing information for the various connectors used (such as connection secrets) to create a flow you can later customize to meet your business needs. For example, you might still need to add required fields specific to your connection, map additional fields, or add or delete steps to meet your use case. You will likely still need to make a few changes before activating the flow. Since templates are pre-built flows, templates not only reduce the barrier to entry and accelerate the time to activate the flow, but also include the best practices for flows. Some examples of templates include: - Cloud-specific templates, such as Service Cloud or Revenue Cloud - Connector-specific templates, such as Salesforce, ServiceNow, NetSuite, or Jira You can search for templates (by template name, connector name, or template description) and filter templates (by use case category or connector). For more information about how to create a new flow from template, refer to [Create a New Flow From Template](https://docs.mulesoft.com/composer/ms_composer_using_a_flow_and_creating_trigger#create-a-new-flow-from-template). Since you will likely need to further customize your flow from a template, consider the following recommendations and guidelines when encountering messages while customizing your flow from a template. Instance Requires Different Fields Your instance might have fields that are different from the template. For example, you might need to add a required field that is not used or delete a field used in the template that does not exist in your connection. These errors must be resolved before testing the flow. Field Does Not Exist With Your Connection The `This field does not exist with your connection` message appears if the input field is not present in your connection. For example, when creating custom fields defined in the prerequisites, the ID of the custom field saved in the template differs from the ID of the custom field created in the instance (even if the name is the same), which causes an error to occur in the flow. You can delete the custom field saved in the template and then re-add your custom field from the field selector. Value Does Not Exist With Your Connection The `This value does not exist with your connection` message appears if the output field (data pill) is not present in your connection. For example, when creating custom fields defined in the prerequisites, the ID of the custom field saved in the template differs from the ID of the custom field created in the instance (even if the name is the same), which causes an error to occur in the flow. You can remove the mapped data pill and select your custom field from the dropdown. ## See Also - [Mulesoft Composer: Overview](https://docs.mulesoft.com/composer/ms_composer_overview) - [MuleSoft Composer: Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) - [Composer Connector Reference](https://docs.mulesoft.com/composer/ms_composer_reference) - [Knowledge Articles](https://help.salesforce.com/s/) --- product: Composer --- # Building Formulas for Flows > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Manipulate data in Composer by building _expressions_ and applying _functions_. Using the **Custom Expression Editor**, create expressions that include functions and mathematical operators. Use the editor also to truncate words, capitalize phrases, and set the date. When building formulas for a flow, keep in mind that: - You can nest functions and use the input parameters of another function call for your function. - Composer functions used in Composer are built using [DataWeave](https://docs.mulesoft.com/dataweave/2.3/dw-operators). - Composer functions treat empty spaces as empty space characters in a formula. ## Access the Custom Expression Editor To access the **Custom Expression Editor**: 1. From the **Composer Flows** tab, open a flow. 2. Click **Edit**. 3. In an action field, in a value in the query builder, or in the value of an **If/Else Block** control, select **Custom Expression fx** from the drop-down menu. The **Custom Expression Editor** appears. ## Add a Custom Expression to an Action When adding a custom expression, place the cursor over elements in the **Custom Expression Editor** window to trigger context popovers containing helpful suggestions and in-app support. To add a custom expression to an action: 1. In the **Custom Expression Editor** left pane, click one of the following tabs: 1. **Function**, to view or search for a function 2. **Data**, to view or search for a field or data pill 3. **Operator**, to view or search for an operator 2. Select the available functions, fields, data pills, or operators for your custom expression from the left pane. Your selections appear in the **** box in the right pane. The syntax of your custom expression is validated automatically. 3. If you want to reuse the expression in the **** box in another field, copy it. 4. After the custom expression is created and validated, click **Apply**. 5. Click **Save**. The custom expression is added to the field. ## Edit a Custom Expression To edit an existing custom expression in an action: 1. From the **Composer Flows** tab, open a flow. 2. Click **Edit** 3. In an action field containing your custom expression, click the pencil icon. The **Custom Expression Editor** appears. 4. In the **** box in the right pane of the **Custom Expression Editor**, either select and delete the existing custom expression or place your cursor where you want to add items from the left pane. 5. In the left pane, select from the available functions, fields, data pills, or operators. Your selections appear in the **** box in the right pane. The syntax of your edited custom expression is validated automatically. 6. After your custom expression is edited and validated, click **Apply**. 7. Click **Save**. Your custom expression is edited. ## Delete a Custom Expression To delete an existing custom expression in an action: 1. From the **Composer Flows** tab, open a flow. 2. Click **Edit** 3. In an action field containing a custom expression, click the X icon. The custom expression is deleted from the field. 4. If your implementation requires this field to contain a value, either add a new custom expression or select a value from the drop-down menu. 5. On the **Flow Details** page, click **Save**. The custom expression is deleted. If your environment requires a value in the custom expression field, your addition or selection is saved. ## See Also - [Mulesoft Composer: Overview](https://docs.mulesoft.com/composer/ms_composer_overview) - [MuleSoft Composer: Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) - [Composer Connector Reference](https://docs.mulesoft.com/composer/ms_composer_reference) - [Knowledge Articles](https://help.salesforce.com/s/) --- product: Composer --- # Building Process Automation with MuleSoft Composer > For the full documentation index, see: https://docs.mulesoft.com/llms.txt MuleSoft Composer (Composer) automates data integration between systems using a no-code, visual interface. You connect different applications and synchronize data in real-time, creating a unified view of customers and business operations without technical expertise. To automate processes with Composer, you build a flow that contains every step in the process: - Selecting the data that you specify from a system such as Google Sheets, Tableau, Workday, or a Salesforce org - Performing actions on the data, such as copying it to another system You choose when to trigger the flow: when something happens, like a change to a record or row, or at intervals of time that you specify. Flows can be as simple or complex as your business needs. ## Example Imagine that a regional Slack user-group tracks its local members in a spreadsheet. Slack users register with the national organization first. Since the national office uses Salesforce to track membership, automatically pushing new members to the regional sheet would save everyone a lot of time. Using Composer, the Salesforce admin can create a single flow that automatically performs this task in near real-time. ![A workflow that describes keeping user information up to date between data silos](/mulesoft/current/en-us/composer/_images/images/overview1.png) This simple flow can be expanded to perform more complex actions, such as writing to different sheets based on the zip code of the new user or propagating changes for existing users. ## Use Cases Some common use cases for Composer include: - **Quote to Cash (ERP Integration)** Drive efficiency and improve sales productivity by automating and streamlining quote-to-cash processes. For example, automatically create sales orders in NetSuite once a Salesforce opportunity closes and automatically notify billing teams in Slack. For more information, refer to the [NetSuite Automation with MuleSoft Composer](https://trailhead.salesforce.com/content/learn/modules/netsuite-data-sync-with-mulesoft-composer) Trailhead module. - **Case Escalation (Ticketing System Integration)** Escalate and resolve cases faster by automating support case management and notification. For example, automatically create a JIRA ticket and automatically send a Slack notification to organize and prioritize urgent support cases from Service Cloud or Zendesk to streamline communication between agents, engineering, and DevOps. For more information, refer to the [Jira Automation with MuleSoft Composer](https://trailhead.salesforce.com/content/learn/modules/jira-data-sync-with-mulesoft-composer) Trailhead module. - **Salesforce to Salesforce** Connect and synchronize data between multiple Salesforce orgs. For example, create or update an object in one Salesforce org and sync the changes to another Salesforce org. For more information, refer to the [Automation Between Orgs with MuleSoft Composer](https://trailhead.salesforce.com/content/learn/modules/data-sync-between-orgs-with-mulesoft-composer) Trailhead module. ## Steps To Create a Flow To create a functioning, real-time integration in Composer, you don’t need coding experience. Simply open Composer, and then create a flow that contains all the steps you need to get data from Point A to Point B: Step 1: Choose or create a connection A connection is the username and password you’ll use to access the data you want to work with, plus the URL where you typically enter those credentials. Some systems require a few additional pieces of information, such as a security token. After you define the connection, you can use it multiple times in the same flow or in different flows that you create. Composer never exposes your credentials, and the connections are available only to you, even if other people are also building flows. Instead of a connection, you can choose to schedule a time when the flow runs, such as every 10 minutes. Step 2: Choose a trigger Every flow that uses a connection starts with a trigger: an event such as creating a new record. This event always triggers the flow to run. The events available to trigger a flow depend on the connection you choose. If a scheduled time is chosen instead of a connection, no trigger is needed, because the flow runs at the chosen interval. Step 3: Define the actions you want to take Define what happens to the data fetched by the trigger, and when those actions should be taken; for example, to fetch all records for a specific time period but only copy over the records that have changed or that are new. You might also want to copy over only some information from each record, rather than the entire record. Using the triggers and actions of Composer, you can make the flow as elaborate or as simple as necessary. If you start the flow at a specified time interval instead of choosing a connection, then you’ll fetch data as part of the first action. Step 4: Test your flow on one record As you define triggers and actions, you see sample data that helps you verify you are building the right steps. You can test every change before making the next one, making it easier to find and correct issues with your flow. Your changes will not appear until you activate the flow. Step 5: Activate the flow After testing, activate the flow in your production org. After the flow is activated, it automatically runs when the conditions in the trigger are met. Step 6: Monitor the behavior of your flow You can see what your flow is doing by looking at the data provided on the flow detail page in Composer. Mapping data between systems and doing exactly the right thing at the right time sometimes feels complicated; however, using Composer helps you break down the logic into the steps required. You can experiment with a flow until you’ve got it working just right, and you can add complexity to it as you discover new use cases. ## Access Composer Access the home page to start using Composer for your business needs: ![Mulesoft Composer Home page](/mulesoft/current/en-us/composer/_images/images/overview-page-ms.png)

1	Overview: View the Composer home page.
2	Flows: Create, test, activate, and monitor your flows.
3	Usage Summary: View your monthly tasks and credit usage per flow for your organization.
4	Templates: Leverage pre-built Composer templates to build your flow.
5	Help: Learn about Composer, explore the product documentation, join the MuleSoft community, or visit the Help center.
6	Create new flow: Create your new flow from scratch or from a template.

## Next Steps 1. Review [How Composer Works](https://docs.mulesoft.com/composer/ms_composer_about_flows) to understand how the different parts of a flow work together to automate processes. 2. Create a plan for your first flow using the [checklist](https://docs.mulesoft.com/composer/ms_composer_checklist). 3. Open Composer and build your first flow. ## Related Resources - [Mulesoft Composer Training](https://blogs.mulesoft.com/news/introducing-mulesoft-composer/) - [Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) - [Composer Connector Reference](https://docs.mulesoft.com/composer/ms_composer_reference) - [Knowledge Articles](https://help.salesforce.com/s/) --- product: Composer --- # Composer Connector Reference > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Each system that connects to MuleSoft Composer (Composer) behaves in different ways depending on how the system stores the information you want to retrieve and manipulate. Review each system reference page to understand which triggers and actions are available. The connectors listed in this documentation are available for MuleSoft Composer (Composer). - [Asana](https://docs.mulesoft.com/composer/ms_composer_asana_reference) - [Box](https://docs.mulesoft.com/composer/ms_composer_box_reference) - [Gmail](https://docs.mulesoft.com/composer/ms_composer_gmail_reference) - [Google BigQuery](https://docs.mulesoft.com/composer/ms_composer_google_bigquery_reference) - [Google Calendar](https://docs.mulesoft.com/composer/ms_composer_google_calendar_reference) - [Google Sheets](https://docs.mulesoft.com/composer/ms_composer_googlesheets_reference) - [HTTP](https://docs.mulesoft.com/composer/ms_composer_http_reference) - [HubSpot](https://docs.mulesoft.com/composer/ms_composer_hubspot_reference) - [Jira](https://docs.mulesoft.com/composer/ms_composer_jira_reference) - [Marketo](https://docs.mulesoft.com/composer/ms_composer_marketo_reference) - [Microsoft Dynamics 365 Business Central](https://docs.mulesoft.com/composer/ms_composer_ms_dynamics_365_business_central_reference) - [Microsoft Teams](https://docs.mulesoft.com/composer/ms_composer_ms_teams_reference) - [NetSuite](https://docs.mulesoft.com/composer/ms_composer_netsuite_reference) - [QuickBooks Online](https://docs.mulesoft.com/composer/ms_composer_quickbooks_reference) - [MuleSoft RPA](https://docs.mulesoft.com/composer/ms_composer_rpa_reference) - [Rest Consumer](https://docs.mulesoft.com/composer/ms_composer_rest_consumer_reference) - [Sage Intacct](https://docs.mulesoft.com/composer/ms_composer_sage_intacct_reference) - [Salesforce](https://docs.mulesoft.com/composer/ms_composer_salesforce_reference) - [Salesforce Marketing Cloud](https://docs.mulesoft.com/composer/ms_composer_salesforce_marketing_cloud_reference) - [SAP S/4HANA Cloud](https://docs.mulesoft.com/composer/ms_composer_sap_s4hana_reference) - [ServiceNow](https://docs.mulesoft.com/composer/ms_composer_servicenow_reference) - [Slack](https://docs.mulesoft.com/composer/ms_composer_slack_reference) - [Snowflake](https://docs.mulesoft.com/composer/ms_composer_snowflake_reference) - [Stripe](https://docs.mulesoft.com/composer/ms_composer_stripe_reference) - [Tableau](https://docs.mulesoft.com/composer/ms_composer_tableau_reference) - [Twilio](https://docs.mulesoft.com/composer/ms_composer_twilio_reference) - [Workday](https://docs.mulesoft.com/composer/ms_composer_workday_reference) - [Xero](https://docs.mulesoft.com/composer/ms_composer_xero_reference) - [Zendesk](https://docs.mulesoft.com/composer/ms_composer_zendesk_reference) - [Zuora](https://docs.mulesoft.com/composer/ms_composer_zuora_reference) ## Related Resources - [Overview](https://docs.mulesoft.com/composer/ms_composer_overview) - [Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) - [Knowledge Articles](https://help.salesforce.com/s/) --- product: Composer --- # Configuring and Managing Flows > For the full documentation index, see: https://docs.mulesoft.com/llms.txt After you collect the information described in [the preparation checklist](https://docs.mulesoft.com/composer/ms_composer_checklist), you can then [build](https://docs.mulesoft.com/composer/ms_composer_using_a_flow_and_creating_trigger), [activate](https://docs.mulesoft.com/composer/ms_composer_activation), and [monitor](https://docs.mulesoft.com/composer/ms_composer_monitoring) your flows. Building a flow involves creating a new flow or cloning an existing flow; adding and testing a trigger; adding and testing each action to be performed by the flow, in the order that you want each action performed; and finally testing the completed new flow before activating it. [Test](https://docs.mulesoft.com/composer/ms_composer_test_flow) each trigger and action as you add it to your flow. ## Flow Details Page Access the **Flow Details** page to see details about your flow: ![The Flow Details page in MuleSoft Composer](/mulesoft/current/en-us/composer/_images/images/flow-details-ms.png)

1	The name of the flow.
2	Details about the flow: Created On: The date on which the flow was created in the time zone set in your browser. Flow ID: The ID of the flow. Flow Owner: The owner of the flow. Last Modified: The date on which the flow was last modified in the time zone set in your browser. Status: The status or the flow. The status can be either active or inactive. Last Triggered: The date on which the flow was most recently triggered. This field displays the last time the flow was triggered by either an Event poll or the Scheduler.
3	The Run History of the flow. Composer stores up to 1000 records per flow and can include only the last two weeks of data. For example, for a flow that produces 10 records per day, you can see the Run History for the last two weeks of data (14 x 10 = 140 records). For a flow that produces 100 records per hour, you can see no more than 10 hours of the Run History. Triggering a flow via the Scheduler always creates an entry in the Run History. An entry in the Run History is only added by an Event trigger when a record is either created or updated and passes any filter condition. Start Date: The date on which the flow started in the time zone set in your browser. End Date: The date on which the flow ended in the time zone set in your browser. Status: The status of the flow. The status can be either `SUCCESS` or `FAILED`. Reference ID: The ID of the record or execution that triggered the flow. For Event triggers, the value in this field is the corresponding Record ID. For events triggered by the Scheduler, a unique Execution ID value is created for the run instance. Error: If a flow fails, the error message for the failure appears.
4	The flow actions. You can delete, clone, or view an active flow. Note that if the flow is inactive, you can edit the flow.
5	The Run History actions. You can refresh the Run History section or filter the section by specified criteria.

## See Also - [Mulesoft Composer: Overview](https://docs.mulesoft.com/composer/ms_composer_overview) - [MuleSoft Composer: Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) - [Composer Connector Reference](https://docs.mulesoft.com/composer/ms_composer_reference) - [Knowledge Articles](https://help.salesforce.com/s/) --- product: Composer --- # Connecting a Flow > For the full documentation index, see: https://docs.mulesoft.com/llms.txt A _connection_ in Composer is a configuration that uses a connector and associated user or system credentials to connect to a system. You can use connections at different steps to perform specific tasks, such as connecting to a system, checking for triggers, and retrieving or manipulating data. ## Access the Connections Page To access the **Connections** page, from the **Composer** home page, click **Connections** in the navigation pane. The **Connections** page enables you to: - Select a connection to view all of the flows currently using that connection. - [Change a connection](#change-a-connection). - [Repair a connection](#repair-a-connection). - [Delete a connection](#delete-a-connection). - Change the name of a connection. To access the **Connections** page, from the **Composer** home page, click **Connections** in the navigation pane. ## Change a Connection You can change connections in a trigger or action for all steps (at the flow level) or for individual steps. For example, you can create a flow using connections to a Salesforce sandbox org, and then after your flow testing is complete, you can change the connection in your trigger and actions to use a production org. You can only change to a connection accessing the same system type. You can’t change a Workday connection to a Google Sheets connection, for example. To change a connection: 1. Open the flow. 2. Click the change icon in the trigger or action that connects to a sandbox: ![A button that says Change the Connection](/mulesoft/current/en-us/composer/_images/images/change-connection.png) 3. Change the connection to an existing connection or to a new connection. - If you change the connection to an existing connection: 1. Select the connection to change to. 2. Optionally, if you want to change the connection for all steps that use this specific connection, select **Change all instances of XXX to XXX in this flow**. 3. Click **Change**. 4. Click **Confirm**. - If you change the connection to a new connection: 1. Click **Add New (Connector Name) Connection**. 2. Enter a value for the **Connection Display Name** field. 3. Optionally, if you want to change the connection for all steps that use this specific connection, select **Change all instances of current connection to the new connection in this flow**. 4. Click **Connect**. 5. In the dialog box, log in to the system and allow access. ## Repair a Connection If your OAuth connection is lost, you can repair the connection by refreshing the access token. To repair a connection: 1. Open the flow. 2. Click **Edit**. 3. Click the change icon in the trigger or action that requires repair, and then click **Change Connection**. 4. Click **Repair**. ## Delete a Connection If you no longer need a specific connection, you can delete it. To delete a connection: 1. [Create a new flow](https://docs.mulesoft.com/composer/ms_composer_using_a_flow_and_creating_trigger#create-a-flow) or add a step to an existing flow. 2. If you create a new flow: 1. Select the connector or system to start your flow. 2. In the **What Should Start This Flow?** window, click the gear icon. 3. If you add a step to an existing flow: 1. Select the connector or system to start your flow. 2. In the **Next Step** window, click the gear icon. 4. In the **Manage Connections** window, next to the connection that you want to delete, click the trashcan. A message appears ensuring that you want to delete the selected connection. A window appears, displaying a list of flows currently using that connection. If the connection is: - Not used in any flows, you can delete the connection. - Used in inactive flows, a list containing the name and count of inactive flows using this connection appears. Deleting this connection will affect the listed flows. If you reopen the inactive flow, you must [select a new connection](#change-a-connection). - Used in active and inactive flows, a list containing the name, count, and status of active and inactive flows using this connection appears. If you choose to delete the connection, secondary confirmation appears. Prior to deleting the connection, Composer will first attempt to stop the flows. 5. Click **Delete**. The connection is deleted. ## See Also - [Mulesoft Composer: Overview](https://docs.mulesoft.com/composer/ms_composer_overview) - [MuleSoft Composer: Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) - [Composer Connector Reference](https://docs.mulesoft.com/composer/ms_composer_reference) - [Knowledge Articles](https://help.salesforce.com/s/) --- product: Composer --- # Gmail Connector Reference > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Gmail is a popular email service used by businesses for a large number of communication purposes. This connector enables productivity by connecting a user’s inbox to other systems like Google Sheets, Salesforce, or Slack. ## Before You Begin Gmail Connector requires third-party app access to access restricted data in Google. Before using the connector, your Google Workspace administrator must [add one of the following client IDs to the list of configured apps](https://support.google.com/a/answer/7281227#trustorlimit&zippy=%2Cmanage-access-to-apps-trusted-limited-or-blocked) to create OAuth connections with Composer: - Production Environment United States: `14294369739-rn5ftpjat2mnofvp3gevkvmik0roioe7.apps.googleusercontent.com` - Production Environment Europe: `14294369739-028kk1tl316tgo3a59rtpl6qq6u22d25.apps.googleusercontent.com` ## Connections To connect to a system, whether it is a source of data or the target where you are sending data, you must create a connection with that system’s required credentials. You typically connect to different systems within a flow and can reuse each connection every time you need to connect. This system requires the following credential information for its connections: Connection Name Enter a connection name that will help you remember the details of this connection. You can reuse connections multiple times in a single flow, and in more than one flow, and the credentials are hidden after you create the connection. Therefore, it’s helpful to provide a name that easily identifies this connection from others. Only you can see the connection. Other users in your Composer app must create their own connections. Username The OAuth username that you use to log in to Google. Password The OAuth password that you use to log in to Google. ## Triggers Each flow starts with either a _scheduler_ or a _trigger_. Schedulers are set to a default frequency of 15 minutes. Triggers, such as "each time a new record is created", are defined by you and provide multiple options related to the data in your system. Triggers use a polling process to actively check for new updates from an external system. The polling frequency is 15 seconds. This system provides the following trigger options: On New Email If you don’t specify a [filter](https://developers.google.com/workspace/gmail/api/guides/labels), this trigger fires on all emails (received, sent, or drafts). To specify a filter, the following field is required: - Filter Criteria For example, use `in:inbox` to limit the trigger to new messages in the inbox ### Polling Frequency For triggers in this connector, the **Polling Frequency** field is required. This field enables you to select how often Composer makes a request to the underling system API to look for changes to records in active flows. You can select a different polling frequency for each flow in your organization. With a shorter frequency, the flow executes more often; however, a shorter frequency consumes more [API calls](https://docs.mulesoft.com/general/automation-credits-usage-and-rates). For example, if you have an order management flow, you might require nearly real-time updates, which can be achieved with a 15-second polling interval (which equates to 5760 API calls per day). In contrast, if your flow updates a pricing catalog, you could poll the flow every hour (which equates to 24 API calls per day). ## Actions After you connect to a system and define the trigger or configure a scheduler, you define the actions that the flow performs. For example, you can copy a record between different systems, such as Workday and Salesforce. The actions you can perform depend on which system you are connected to. This system provides the following actions: Send email Sends an email. The following fields are required: - To - Subject - Body To send an email with attachments, the following additional fields are required: - Attachment content - Attachment name Get Attachments Retrieves all attachments from an email. Images that are attached to an email using the clip icon are considered attachments, but images that are dragged into the body of an email are considered embedded images and not attachments. The following field is required: - Message Id The Google Gmail connector’s use and transfer to any other application of information received from Google APIs is subject to the [Google API Services User Data Policy](https://developers.google.com/terms/api-services-user-data-policy#additional_requirements_for_specific_api_scopes), including the Limited Use requirements. **Gmail™ is a trademark of Google LLC.** ## See Also - [Mulesoft Composer: Overview](https://docs.mulesoft.com/composer/ms_composer_overview) - [MuleSoft Composer: Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) - [Composer Connector Reference](https://docs.mulesoft.com/composer/ms_composer_reference) - [Knowledge Articles](https://help.salesforce.com/s/) --- product: Composer --- # Google BigQuery Connector Reference > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Google BigQuery is a cloud data warehouse that enables customers to store and access their data while also offering tooling to run real-time analytics across datasets. ## Before You Begin - To use Google BigQuery Connector, you must have a [Google Workspace](https://support.google.com/a/users/answer/9389764?hl=en&ref_topic=9296556&sjid=17545113492625404882-NA) account. Connections from Composer to personal Google accounts are not permitted. When you connect to your Google Workspace account, a message appears indicating that the Composer is an [unverified app](https://support.google.com/cloud/answer/7454865?hl=en). This behavior is expected. To bypass this message and use the connector, on the **Google hasn’t verified this app** dialog, click **Advanced** > **Use anyway**. - Google BigQuery Connector requires third-party app access to access restricted data in Google. Before using the connector, your Google Workspace administrator must [add the following client ID to the list of configured apps](https://support.google.com/a/answer/7281227#trustorlimit&zippy=%2Cmanage-access-to-apps-trusted-limited-or-blocked) to create OAuth connections with Composer: `292130641403-rlgmr379unk36nuvpba0sd1u3u9c6vap.apps.googleusercontent.com` ## Connections To connect to a system, whether it is a source of data or the target where you are sending data, you must create a connection with that system’s required credentials. You typically connect to different systems within a flow and can reuse each connection every time you need to connect. This system requires the following credential information for its connections: Connection Display Name Enter a connection name that will help you remember the details of this connection. You can reuse connections multiple times in a single flow, and in more than one flow, and the credentials are hidden after you create the connection. Therefore, it’s helpful to provide a name that easily identifies this connection from others. Only you can see the connection. Other users in your Composer app must create their own connections. Project ID The project ID from Google BigQuery. Username The OAuth username that you use to log into Google BigQuery. Password The OAuth password that you use to log into Google BigQuery. ## Data Types The following data types are supported by Google BigQuery Connector: - INT64 - BIGNUMERIC - BOOL - BYTES - DATE - DATETIME - FLOAT64 - JSON - NUMERIC - STRING - TIME - TIMESTAMP ## Triggers Each flow starts with either a _scheduler_ or a _trigger_. Schedulers are set to a default frequency of 15 minutes. Triggers, such as "each time a new record is created", are defined by you and provide multiple options related to the data in your system. Triggers use a polling process to actively check for new updates from an external system. The polling frequency is 15 seconds. This system provides the following trigger options: > [!NOTE] For the given project ID, US-based datasets are retrieved. On New Row Source Returns all new rows of a table based on a watermark every 15 seconds. Provide a value for the following fields: - **Dataset name** - **Table name** - **New Watermark Column**: The following column data types are available for this field: - DATE - DATETIME On New or Updated Row Source Returns all new or updated rows of a table based on a watermark every 15 seconds. Provide a value for the following fields: - **Dataset name** - **Table name** - **New Watermark Column**: The following column data types are available for this field: - DATE - DATETIME - **Update Watermark Column**: The following column data types are available for this field: - DATE - DATETIME ### Polling Frequency For triggers in this connector, the **Polling Frequency** field is required. This field enables you to select how often Composer makes a request to the underling system API to look for changes to records in active flows. You can select a different polling frequency for each flow in your organization. With a shorter frequency, the flow executes more often; however, a shorter frequency consumes more [API calls](https://docs.mulesoft.com/general/automation-credits-usage-and-rates). For example, if you have an order management flow, you might require nearly real-time updates, which can be achieved with a 15-second polling interval (which equates to 5760 API calls per day). In contrast, if your flow updates a pricing catalog, you could poll the flow every hour (which equates to 24 API calls per day). ## Actions After you connect to a system and define the trigger or configure a scheduler, you define the actions that the flow performs. For example, you can copy a record between different systems, such as Workday and Salesforce. The actions you can perform depend on which system you are connected to. This system provides the following actions: Insert Rows Updates a table by inserting one or more rows into the table. Provide a value for **SQL string**. Update Rows Updates a set of rows. Provide a value for **SQL string**. Delete Rows Deletes a set of rows. Provide a value for **SQL string**. Select Rows Retrieves a set of rows. Provide a value for **SQL string**. ## Input Parameters Query statements can include parameter values by adding `:` before the parameter name, such as `Select field from dataset.table where field = :param1`. You can define a value for the parameter in the **Input Parameters** section. For example, if you define `param1` as `12345`, the query statement is `Select field from dataset.table where field = 12345`. You must define a value for the parameter as either a literal string or an output value from previous actions. Note that input parameter values of String or date data types must be provided between single quotes using the expression editor. For literal strings, add the single quotes to the value in the editor, such as `’12345’`. For an output value from previous actions, select the custom expression option, add the single quotes to the custom expression in the editor, and apply the changes, such as `’Field From Previous Step’`. **Google BigQuery™ is a trademark of Google LLC.** ## See Also - [Mulesoft Composer: Overview](https://docs.mulesoft.com/composer/ms_composer_overview) - [MuleSoft Composer: Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) - [Composer Connector Reference](https://docs.mulesoft.com/composer/ms_composer_reference) - [Knowledge Articles](https://help.salesforce.com/s/) --- product: Composer --- # Google Calendar Connector Reference > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Google Calendar is a calendar and task planning application by Google that focuses on enhancing personal and team productivity. Using Google Calendar, individuals can easily schedule tasks and meetings. They can also share events with colleagues through an easy-to-use calendar interface. ## Connections To connect to a system, whether it is a source of data or the target where you are sending data, you must create a connection with that system’s required credentials. You typically connect to different systems within a flow and can reuse each connection every time you need to connect. This system requires the following credential information for its connections: Connection Name Enter a connection name that will help you remember the details of this connection. You can reuse connections multiple times in a single flow, and in more than one flow, and the credentials are hidden after you create the connection. Therefore, it’s helpful to provide a name that easily identifies this connection from others. Only you can see the connection. Other users in your Composer app must create their own connections. Username The OAuth username that you use to log in to Google. Password The OAuth password that you use to log in to Google. ## Actions After you connect to a system and define the trigger or configure a scheduler, you define the actions that the flow performs. For example, you can copy a record between different systems, such as Workday and Salesforce. The actions you can perform depend on which system you are connected to. This system provides the following actions: Create a new event Creates an event. The following fields are required: - Calendar ID - Start Time - End Time Update an event Updates an event. The following fields are required: - Calendar ID - Event ID - Start Time - End Time If entering a custom dateTime data pill, ensure the time entered uses the UTC +0 ("Zulu") timezone. For example, January 1, 2022, at 9:00 AM Pacific Time (UTC-7) is entered as **2022-01-01, 04:00pm** Google Calendar Connector’s use and transfer to any other application of information received from Google APIs is subject to the [Google API Services User Data Policy](https://developers.google.com/terms/api-services-user-data-policy#additional_requirements_for_specific_api_scopes), including the Limited Use requirements. **Google Calendar™ is a trademark of Google LLC.** ## See Also - [Mulesoft Composer: Overview](https://docs.mulesoft.com/composer/ms_composer_overview) - [MuleSoft Composer: Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) - [Composer Connector Reference](https://docs.mulesoft.com/composer/ms_composer_reference) - [Knowledge Articles](https://help.salesforce.com/s/) --- product: Composer --- # Google Sheets Connector Reference > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Use Google Sheets as a data source (get a new Google Sheet row and send a Slack message with information from the row, for example) or a data target (get a new Salesforce contact and turn it into a row in a Google Sheet). Some details of how to work with data in a flow are specific to the data source or data target, and also change depending on the specific trigger or actions you choose. ## Before You Begin Google Sheets Connector requires third-party app access to access restricted data in Google. Before using the connector, your Google Workspace administrator must [add the following client ID to the list of configured apps](https://support.google.com/a/answer/7281227#trustorlimit&zippy=%2Cmanage-access-to-apps-trusted-limited-or-blocked) to create OAuth connections with Composer: `250037406766-pm8dppphhfm9ugr6rtmdk1unrr48oi3h.apps.googleusercontent.com` ## Connections To connect to a system, whether it is a source of data or the target where you are sending data, you must create a connection with that system’s required credentials. You typically connect to different systems within a flow and can reuse each connection every time you need to connect. This system requires the following credential information for its connections: Connection Name Enter a connection name that will help you remember the details of this connection. You can reuse connections multiple times in a single flow, and in more than one flow, and the credentials are hidden after you create the connection. Therefore, it’s helpful to provide a name that easily identifies this connection from others. Only you can see the connection. Other users in your Composer app must create their own connections. Composer launches an authentication dialog where you choose which Google Drive account you’re connecting to Composer, and if you aren’t already logged in, you enter a username and password. ## Triggers Each flow starts with either a _scheduler_ or a _trigger_. Schedulers are set to a default frequency of 15 minutes. Triggers, such as "each time a new record is created", are defined by you and provide multiple options related to the data in your system. Triggers use a polling process to actively check for new updates from an external system. The polling frequency is 15 seconds. This system provides the following trigger options: New spreadsheet This trigger fires when a new spreadsheet is created in the Google Drive associated with the connection. Google Sheets are not saved at the moment of creation. They are saved the first time they are edited. Therefore, a new spreadsheet won’t trigger a flow until after it is edited and saved. However, the save date is the time of creation, not the first edit. Thus, if you create a second spreadsheet and edit it before you edit the first one, the second spreadsheet triggers a flow; the first one is ignored. New row in sheet Monitors one sheet within a spreadsheet and triggers when a new row is added at the end of the sheet. When a flow is initiated, this trigger returns up all existing rows in the sheet. Each subsequent time that the flow is triggered, new rows added to the sheet are returned. Once text is present in one cell or column, updating those cells or columns does not trigger as a new row. To trigger a new row when updating a cell or column, use the **Update row in sheet** trigger. Updated row in sheet Monitors one sheet within a spreadsheet and triggers when a row is created or updated. When a flow is initiated, this trigger returns all existing rows in the sheet. Each subsequent time that the flow is triggered, new or updated rows in the sheet are returned. ### Limits - Sheets limited to 10,000 rows - Header rows excluded - Trigger works with My Drive, not Shared Drive ### Polling Frequency For triggers in this connector, the **Polling Frequency** field is required. This field enables you to select how often Composer makes a request to the underling system API to look for changes to records in active flows. You can select a different polling frequency for each flow in your organization. With a shorter frequency, the flow executes more often; however, a shorter frequency consumes more [API calls](https://docs.mulesoft.com/general/automation-credits-usage-and-rates). For example, if you have an order management flow, you might require nearly real-time updates, which can be achieved with a 15-second polling interval (which equates to 5760 API calls per day). In contrast, if your flow updates a pricing catalog, you could poll the flow every hour (which equates to 24 API calls per day). ## Actions After you connect to a system and define the trigger or configure a scheduler, you define the actions that the flow performs. For example, you can copy a record between different systems, such as Workday and Salesforce. The actions you can perform depend on which system you are connected to. This system provides the following actions: Create row This action adds a new row at the end of the sheet named in the connection. Update row This action updates a row in a sheet. ### Limits - A Google Sheet must have a header row. If data is stored in row #1, the action fails. - Google Sheets does not write to a cell if the composite data pill has a null or empty value. This could affect the **Update row** or **Create row** actions. **Google Sheets™ is a trademark of Google LLC.** ## See Also - [Mulesoft Composer: Overview](https://docs.mulesoft.com/composer/ms_composer_overview) - [MuleSoft Composer: Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) - [Composer Connector Reference](https://docs.mulesoft.com/composer/ms_composer_reference) - [Knowledge Articles](https://help.salesforce.com/s/) --- product: Composer --- # How Composer Works > For the full documentation index, see: https://docs.mulesoft.com/llms.txt A flow defines the automated processes between two or more systems. Think of it as the schema for an entire automation process. For example, you can automate any of these actions with Composer: - Copy all new records in one Salesforce org and replicate them in another. - Create employee records or job requisitions in Workday, and populate some of the fields with data from another system. - Check a source of data every fifteen minutes, and if the data changed, copy those changes to a Tableau data source. You can also combine multiple actions in a single flow, such as replicating Salesforce records and then sending a Slack message to a particular channel based on the record type. Understanding how the basic building blocks of a flow work together makes it easier to confidently build and test flows. Building a flow is a simple matter of adding a trigger and all the actions you want to perform to complete an automated process. ## Triggers The first step of the flow is always a trigger. The options available depend on which connection or schedule you choose: - If you choose a time interval instead of an event, you won’t see any options: the trigger is finished, and you are ready to create the actions that define what this flow does. - If you choose a connection, define what kind of data triggers the flow and is fetched, available for the actions you’ll define next. The following example shows a trigger that uses a connection: ![A configuration example of a Salesforce trigger](/mulesoft/current/en-us/composer/_images/images/trigger-example.png) - **Trigger** is the name of the trigger, a name you provide. - **Salesforce Org HQ** is the name of the connection which this trigger uses as the data source. The trigger listens to the data source and starts when an event specified in the next field occurs, or when a time interval is reached. - **Start this flow when:** is a list of actions that can start a flow for the chosen connection. Click in the text box to see a list of options. - **Object type** is a list of objects you can choose, such as account or opportunity for a Salesforce connection. The label here and the choices you are given depend on the connection. - **Result fields** by default lists the number of fields that will be available to the flow each time it is triggered. To work with only some record fields, click **Select Fields**. - **Sample Output** shows you the field name and a sample value taken from an actual record in the data source you connected to. Check the sample output to confirm that you’ve connected to the correct account. It also helps you understand the data that you’ll be able to work with. To see the API Name of the field, hover over the information bubble next to each field name. You can test your trigger and adjust as needed. Simply click **Test**, then make the system event happen: in this example, create a new Salesforce contact. If the test completes without errors, you’re ready for the next step: define the actions that this flow will perform after being triggered. ### Choosing Between Using Connections or a Scheduler After you create and name a flow, choose what triggers the flow: an event in a system such as Salesforce or Workday (creating a connection), or a time interval specified by a Scheduler, such as "every fifteen minutes. Triggering a flow with an event is done with a connection, and triggering with a time schedule is done with Scheduler. ![A connection dialog that shows a list of systems that can trigger a flow](/mulesoft/current/en-us/composer/_images/images/connection-example.png) #### Triggering Flows by Using Connections Using connections to trigger flows protects your login credentials while giving easy access to data sources: - Only you can see the connections you create. - Your credentials are never exposed or accessible after you create a connection to replace them. - You can’t change the name of a connection after it is used in a flow that is deployed. The first step in triggering a flow is connecting to the system where the trigger will occur. In the **What Should Start This Flow** dialog, choose or create a connection as the first step of creating a trigger: - Choose an existing connection from the list. - Click **Add New Connection** to create a new connection that is automatically selected after you create it. - Manage connections by changing connection names or deleting connections. #### Triggering Flows by Using a Scheduler Instead of using connections to trigger a flow, you can use the **Scheduler** control to create a time interval that triggers a flow: ![A dropdown menu with a list of time intervals, including 15 minutes, 30 minutes, 45 minutes, 1 hour, 5 hours, and 1 day](/mulesoft/current/en-us/composer/_images/images/connection-scheduler.png) ## Actions An action is a step in the flow. You create the first action of the flow right after the trigger, and as with the trigger, you can choose a connection. You’ll have access to the data fetched by the trigger and any previous actions as well. However, you can also start with a flow control before the action. ![A dialog for adding an action](/mulesoft/current/en-us/composer/_images/images/create-an-action.png) In the following example, a Salesforce admin has created an action, named it, and chosen a connection to their Google spreadsheets, as you can see in the top banner of the action. The admin has also defined the action: in this case, create a new row in a spreadsheet and populate it with some fields from the flow trigger (each new contact record). ![A step in the example action configuration to create a new row in a spreadsheet](/mulesoft/current/en-us/composer/_images/images/action-step1.png) - **Action** is the task you want to perform. The actions you can choose from depend on which connection you choose. The rest of the fields in this section depend on the connection type, and the action you choose. - **Spreadsheet ID** is the name of the spreadsheet this action will use. You can search for and select any of the spreadsheets that you can access using the credentials you used to create the connection. - **Worksheet** is the name of the worksheet where you will add a row. - **Columns** is the area where you map the trigger fields to columns in the spreadsheet. This area, like the others, is different for different systems. In this example, click **Add Columns** to see all the columns from the spreadsheet listed and choose the ones you want to work with here: ![A step in the example action configuration to populate fields of a spreadsheet column](/mulesoft/current/en-us/composer/_images/images/action-step2.png) Choose which fields you want to act upon, and then map the fields you fetched with the trigger or previous actions with these: ![A step in the example action configuration to map fields](/mulesoft/current/en-us/composer/_images/images/action-step3.png) Map the fields delivered by the trigger to the spreadsheet rows you selected. In this example, **Email**, **FirstName**, and **LastName** will be mapped to the Google sheet columns **Email**, **First Name**, and **Last Name**. You don’t have to map all the fields fetched in your action or trigger connection. Remember, the selection pane (**Columns**) is different depending on the connection for this action and other choices. For a list of valid actions for each connection, see the reference topic for the system you are interested in. This is the complete action, ready for testing: ![All the steps in the example action configuration](/mulesoft/current/en-us/composer/_images/images/action-overview.png) The fields from Salesforce that are mapped to the Google Sheet fields are data pills, containers for everything that might be in a field (or other resource, depending on the connection). ## Data Pills Data pills contain the complexity of a data structure, making it easy to map data from triggers or previous actions. Using data pills, data mapping can be as simple or as complex as you need: - You can concatenate two or more data pills by mapping them to the same field, column, or other data target. - You can create a custom expression instead of simply mapping data pills to data targets, by select **Custom Express fx**. For example, you might want to add some text such as `Copied from Salesforce` after a data pill, to flag it for inspection. - You can construct a list of strings with multiple comma-separated data pills and manually-entered string values. If you enter a single data pill, Composer automatically converts that data pill to a list. When using the `list of strings` data pill, if you also select a data pill of the data type `string`, `number`, `boolean` or `date`, those data pills are appended to the existing list and the non-string data pills will be typecast to a `string` data type. If a data pill is a field with a null or blank value, and you map it to an optional field, Composer removes it from the flow. If you map it to a required field, an error occurs because a value is required. ## Flow Controls If you need to add logic to your flow beyond a basic action, you can use a For Each loop or an If/Else block. You’ll define the flow control and then specify the action to be taken based on the logic applied to the data fetched previously. ### For Each Loop A For Each loop acts on each record in a list. For example, if the flow fetches a set of contacts from Salesforce, you can loop through the list and copy each record to a row in a Google Sheet. ![An example action configuration with the For Each loop](/mulesoft/current/en-us/composer/_images/images/for-each-example.png) **Input list** is chosen from the list of records available from a previous action. In this example, a previous action fetched all the contact records associated with a single account. The rest of the steps are the actions that are to be performed on each record in the list. In this example, the action writes contacts to a Google Sheet, one record per row. ### If/Else Block An If/Else block takes a single record and checks to see if it meets conditions you specify. If it does, you define what actions to take. ![An example action configuration with the If Else block](/mulesoft/current/en-us/composer/_images/images/if-else-example.png) This example shows only one If branch: if the phone number on the record starts with `702`, then the first and last names are copied to a row in a Google Sheet. If a record doesn’t meet the criteria, no action is taken, and the flow moves on to the next action, since there is only one branch. You can add up to 20 conditions per branch and as many actions per branch as you need. Click **Add If** to add branches. After specifying all the branches you need, you can specify a fall-through action with **Add Else**. Be careful how you order your If statements. The action specified by the first branch whose conditions are met is the only action performed in the If/Else block. ## Test You can test your work after every trigger and action. As you test, you can add or delete triggers, actions, and flow controls. You can also change the connection you use in triggers or actions to another connection of the same system type. After testing is complete, you are ready to activate your flow. ## Related Resources - [Mulesoft Composer: Overview](https://docs.mulesoft.com/composer/ms_composer_overview) - [MuleSoft Composer: Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) - [Configuring and Managing Flows](https://docs.mulesoft.com/composer/ms_composer_flows) - [Activating a Flow](https://docs.mulesoft.com/composer/ms_composer_activation) - [Monitoring a Flow](https://docs.mulesoft.com/composer/ms_composer_monitoring) - [Knowledge Articles](https://help.salesforce.com/s/) --- product: Composer --- # HTTP Connector Reference > For the full documentation index, see: https://docs.mulesoft.com/llms.txt HTTP Connector connects cloud applications that are not currently supported through dedicated connectors. Use HTTP Connector to connect to systems that Composer does not currently support to extend the capabilities of the systems that Composer does support. HTTP Connector for Composer uses [HTTP](https://www.digitalocean.com/community/tutorials/http-1-1-vs-http-2-what-s-the-difference#http-1-1) 1.1 to handle JSON data. ## Connections To connect to a system, whether it is a source of data or the target where you are sending data, you must create a connection with the required credentials of that system. You typically connect to different systems within a flow and can reuse each connection every time you need to connect. Provide the following connection information: > [!NOTE] The HTTP response timeout is 60 seconds and cannot be changed. Connection Name Enter a connection name that will help you remember the details of this connection. You can reuse connections multiple times in a single flow, and in more than one flow, and the credentials are hidden after you create the connection. Therefore, it’s helpful to provide a name that easily identifies this connection from others. Only you can see the connection. Other users in your Composer app must create their own connections. Base URL The default location URL for the cloud application that the connection uses. Authorization The following authorization options are available: - **OAuth 2.0 Client Credentials** The OAuth 2.0 Client Credentials obtain an access token from a user-defined path. Provide a value for the following fields: - **Base URL** - **Client ID** - **Client Secret** - **Token URL** - **API Key** The API Key connects to applications without explicitly defining a user. You must add this key to all requests, and the cloud application identifies the origin of the request and completes the authorization. Provide a value for the following fields: - **Base URL** - **Name** - **Value** - **Sent As**: Select one of the following values: - **Header**: If selected, Composer adds the following header to the request: `Name: Value`. - **Query Parameter**: If selected, Composer adds the following query parameter to the request: `Name=Value`. - **Basic Authentication** The Basic Authentication method enables an HTTP user agent to provide a username and password when making an HTTP request. Provide a value for the following fields: - **Base URL** - **Username** - **Password** - **Bearer Token Authorization** Bearer Token Authorization is the authentication process that sends a header named `Authorization` with a value of `Bearer` and a token with every request. Provide a value for the following fields: - **Base URL** - **Token** ### Connect Your Target System in Composer Using OAuth 2.0 Using HTTP Connector, you can establish a connection with an [OAuth 2.0 Authorization Code Grant](https://auth0.com/intro-to-iam/what-is-oauth-2) to enable authorization. With this authorization, you can then access resources hosted by other apps such as Salesforce, Gmail, or Outlook 365. Before establishing a connection, you must create an OAuth Client in the target system. The process for creating an OAuth Client depends on each target system. The following tables provide configuration examples and details about required fields when connecting to a target system using an OAuth client: #### Fortnox > [!NOTE] To use the same **Client ID** and **Client Secret** in different flows, use the same > Composer connection and consider the allowed requests per minute. To use different Composer > connections, use different Fortnox environments.

Step	Field	Example Value	Notes
Connect to your HTTP Account	Connection Display Name	`Fort Nox at admin@1342287`	This should be your user.
	Authorization Type	`OAuth 2.0 Authorization Code`	The value in this field is fixed.
	Base URL	`https://api.fortnox.se`
	Client ID	`NmE4OTUzY2…`
	Client Secret	`wMTUtZWV…`
	Scopes	`companyinformation`	For all available scopes, see OAuth 2.0 Scopes for Fortnox APIs.
	Authorization URL	`https://apps.fortnox.se/oauth-v1/auth`	You must register your callback URL on the Fortnox account created application. Fortnox allows you to specify only one callback URL by application, so you must create different applications to specify different environment callback URLs.
	Authorization URL Query Parameters	Parameter 1: Key: `access_type` Value: `offline`
	Token Exchange URL	`https://apps.fortnox.se/oauth-v1/token`
	Token Exchange Headers	Parameter 1: Key: `Authorization` Value: `Basic NmE4OTUzY2MtMTk2Zi00MjZiLTgwMTUtZWVjMjY1OWI1MzAx`	Fortnox requires a Basic authentication header in the `Basic CREDENTIALS` format, where CREDENTIALS is the Base64 encoding of Client ID and Client Secret, separated with a colon. For example: Client ID: `8VurtMGDTeAI` Client Secret: `yFKwme8LEQ` Credentials: `OFZ1cnRNR0RUZUFJOnlGS3dtZThMRVE=` For more information, see Authentication.
	Token Refresh URL	`https://apps.fortnox.se/oauth-v1/token`
	Token Refresh Headers	Parameter 1: Key: `Authorization` Value: `Basic NmE4OTUzY2MtMTk2Zi00MjZiLTgwMTUtZWVjMjY1OWI1MzAx`	Fortnox requires a Basic authentication header in the `Basic CREDENTIALS` format, where CREDENTIALS is the Base64 encoding of Client ID and Client Secret, separated with a colon. For example: Client ID: `8VurtMGDTeAI` Client Secret: `yFKwme8LEQ` Credentials: `OFZ1cnRNR0RUZUFJOnlGS3dtZThMRVE=` For more information, see Authentication.
	Access Token Expired Code	`401`
Test HTTP Connection	Request Method	`Get`
Test HTTP Connection	Request Path	`/3/companyinformation`

#### Gmail

Step	Field	Example Value	Notes
Connect to your HTTP Account	Connection Display Name	`Gmail john.smith@gmail.com connection`	Including the Gmail email address aids in identifying the connection from a list.
	Authorization Type	`OAuth 2.0 Authorization Code`	The value in this field is fixed.
	Base URL	`https://gmail.googleapis.com`
	Client ID	`181298210352-mt5.apps.googleusercontent.com`
	Client Secret	`YmmkNirf6zDc512u7MvPoJebP…`
	Scopes	`https://www.googleapis.com/auth/gmail.send https://www.googleapis.com/auth/gmail.readonly`	For all available scopes, see OAuth 2.0 Scopes for Google APIs.
	Authorization URL	`https://accounts.google.com/o/oauth2/v2/auth`
	Authorization URL Query Parameters	Parameter 1: Key: `access_type` Value: `offline` Parameter 2: Key: `prompt` Value: `consent`
	Token Exchange URL	`https://oauth2.googleapis.com/token`
	Token Refresh URL	`https://oauth2.googleapis.com/token`
	Token Revoke URL	`https://oauth2.googleapis.com/revoke`
	Access Token Expired Code	`401`
Test HTTP Connection	Request Method	`Get`
Test HTTP Connection	Request Path	`/gmail/v1/users/me/profile`	For more information, see the Gmail API documentation.

#### Google Calendar

Step	Field	Example Value	Notes
Connect to your HTTP Account	Connection Display Name	`Calendar at john.smith@gmail.com`	Including the Gmail email address aids in identifying the connection from a list.
	Authorization Type	`OAuth 2.0 Authorization Code`	The value in this field is fixed.
	Base URL	`https://www.googleapis.com/calendar`
	Client ID	`181298210352-mt5.apps.googleusercontent.com`
	Client Secret	`YmmkNirf6zDc512u7MvPoJebP…`
	Scopes	`https://www.googleapis.com/auth/calendar.events` `https://www.googleapis.com/auth/calendar.readonly`	For all available scopes, see OAuth 2.0 Scopes for Google APIs.
	Authorization URL	`https://accounts.google.com/o/oauth2/v2/auth`
	Authorization URL Query Parameters	Parameter 1: Key: `access_type` Value: `offline` Parameter 2: Key: `prompt` Value: `consent`
	Token Exchange URL	`https://oauth2.googleapis.com/token`
	Token Refresh URL	`https://oauth2.googleapis.com/token`
	Token Revoke URL	`https://oauth2.googleapis.com/revoke`
	Access Token Expired Code	`401`
Test HTTP Connection	Request Method	`Get`
Test HTTP Connection	Request Path	`/v3/users/me/settings`	For more information, see the Google Calendar API documentation.

#### Google Sheets

Step	Field	Example Value	Notes
Connect to your HTTP Account	Connection Display Name	`Google Sheets at john.smith@gmail.com`	Including the Gmail email address aids in identifying the connection from a list.
	Authorization Type	`OAuth 2.0 Authorization Code`	The value in this field is fixed.
	Base URL	`https://www.googleapis.com`
	Client ID	`181298210352-mt5.apps.googleusercontent.com`
	Client Secret	`YmmkNirf6zDc512u7MvPoJebP…`
	Scopes	`https://www.googleapis.com/auth/spreadsheets` `https://www.googleapis.com/auth/drive.readonly` `https://www.googleapis.com/auth/drive.metadata.readonly`	For more information, see the Google Drive API-specific authorization and authentication information documentation.
	Authorization URL	`https://accounts.google.com/o/oauth2/v2/auth`
	Authorization URL Query Parameters	Parameter 1: Key: `access_type` Value: `offline` Parameter 2: Key: `prompt` Value: `consent`
	Token Exchange URL	`https://oauth2.googleapis.com/token`
	Token Refresh URL	`https://oauth2.googleapis.com/token`
	Token Revoke URL	`https://oauth2.googleapis.com/revoke`
	Access Token Expired Code	`401`
Test HTTP Connection	Request Method	`Get`
Test HTTP Connection	Request Path	`/drive/v3/about?fields=user`	For more information, see the Google Drive API-specific authorization and authentication information documentation.

#### Hubspot

Step	Field	Example Value	Notes
Connect to your HTTP Account	Connection Display Name	`Hubspot Composer DEMO org`	Including the Hubspot organization name aids in identifying the connection from a list.
	Authorization Type	`OAuth 2.0 Authorization Code`	The value in this field is fixed.
	Base URL	`https://api.hubapi.com/`
	Client ID	`63ddf8b7-c7b0-40f9-804…`	For more information, see the Hubspot documentation.
	Client Secret	`2100f863-944c-433c-a…`
	Scopes	`settings.users.read` `crm.lists.read` `settings.users.teams.read` `crm.schemas.contacts.read`
	Authorization URL	`https://app.hubspot.com/oauth/authorize`
	Token Exchange URL	`https://api.hubapi.com/oauth/v1/token`
	Token Refresh URL	`https://api.hubapi.com/oauth/v1/token`
	Access Token Expired Code	`401`
Test HTTP Connection	Request Method	`Get`
Test HTTP Connection	Request Path	`contacts/v1/lists/all/contacts/all?count=1` `https://api.hubapi.com/application/settings/test/v1/actions/accounts-fetch`	For more information, see the Hubspot OAuth 2.0 documentation.

#### Jira

Step	Field	Example Value	Notes
Connect to your HTTP Account	Connection Display Name	`Jira at ocs.citizen.demo@gmail.com (STG)`	Including the Gmail email address aids in identifying the connection from a list.
	Authorization Type	`OAuth 2.0 Authorization Code`	The value in this field is fixed.
	Base URL	`https://api.atlassian.com/ex/jira/077bc6b6-f2ab-4cd6-a694-c469cb2d058d/rest/api/3`	The value in this field is the Cloud ID for your Jira account, which is the Tenant ID parameter in the Base URL field.
	Client ID	`SgPehF9AZ5ECD63iUJpG2aPO3j9qNvXM`
	Client Secret	`Yf8q-wbEJjeJIhx5iuE-BiydpL1oCj7wVy2gaoYDEMCe4xwWO_Q2vbjyJg6rGmD7L`
	Scopes	`offline_access` `read:jira-work` `manage:jira-project` `read:jira-user` `write:jira-work`
	Authorization URL	`https://auth.atlassian.com/authorize`	You must register your callback URL when creating a Jira account. As a result, these credentials only work in staging environments.
	Authorization URL Query Parameters	Parameter 1: Key: `audience` Value: `api.atlassian.com` Parameter 2: Key: `prompt` Value: `consent`
	Token Exchange URL	`https://auth.atlassian.com/oauth/token`
	Token Refresh URL	`https://auth.atlassian.com/oauth/token`
	Access Token Expired Code	`401`
Test HTTP Connection	Request Method	`Get`
Test HTTP Connection	Request Path	`/myself`

#### Microsoft Teams

Step	Field	Example Value	Notes
Connect to your HTTP Account	Connection Display Name	`My Microsoft Teams connection`	Including the Microsoft Teams instance name aids in identifying the connection from a list.
	Authorization Type	`OAuth 2.0 Authorization Code`	The value in this field is fixed.
	Base URL	`https://graph.microsoft.com`
	Client ID	`1c325c1c-8fd5-419f-85dc-a69cc2f30a21`
	Client Secret	`P8M8Q~nAXXckZeqGxR-gE3WJIOsw~rIkjdG8jc7G`
	Scopes	`https://graph.microsoft.com/Mail.Read` `https://graph.microsoft.com/User.Read` `offline_access`
	Authorization URL	`https://login.microsoftonline.com/9d7ee99b-dadd-4dfa-9bba-323e2f1f63b3/oauth2/v2.0/authorize`	Tenant ID value: `https://login.microsoftonline.com/9d7ee99b-dadd-4dfa-9bba-323e2f1f63b3/oauth2/v2.0/authorize`
	Token Exchange URL	`https://login.microsoftonline.com/9d7ee99b-dadd-4dfa-9bba-323e2f1f63b3/oauth2/v2.0/token`
	Token Refresh URL	`https://login.microsoftonline.com/9d7ee99b-dadd-4dfa-9bba-323e2f1f63b3/oauth2/v2.0/token`
	Access Token Expired Code	`401`
Test HTTP Connection	Request Method	`Get`
Test HTTP Connection	Request Path	`/v1.0/me`

#### Outlook 365

Step	Field	Example Value	Notes
Connect to your HTTP Account	Connection Display Name	`My Outlook 365 connection`	Including the Outlook instance name aids in identifying the connection from a list.
	Authorization Type	`OAuth 2.0 Authorization Code`	The value in this field is fixed.
	Base URL	`https://graph.microsoft.com`
	Client ID	`1c325c1c-8fd5-419f-85dc-a69cc2f30a21`
	Client Secret	`P8M8Q~nAXXckZeqGxR-gE3WJIOsw~rIkjdG8jc7G`
	Scopes	`https://graph.microsoft.com/Mail.Read` `https://graph.microsoft.com/User.Read` `offline_access`
	Authorization URL	`https://login.microsoftonline.com/9d7ee99b-dadd-4dfa-9bba-323e2f1f63b3/oauth2/v2.0/authorize`
	Token Exchange URL	`https://login.microsoftonline.com/9d7ee99b-dadd-4dfa-9bba-323e2f1f63b3/oauth2/v2.0/token`
	Token Refresh URL	`https://login.microsoftonline.com/9d7ee99b-dadd-4dfa-9bba-323e2f1f63b3/oauth2/v2.0/token`
	Access Token Expired Code	`401`
Test HTTP Connection	Request Method	`Get`
Test HTTP Connection	Request Path	`/v1.0/me` -OR- `/v1.0/me/mailfolders/inbox/messages?$select=subject,from,receivedDateTime&$top=25&$orderby=receivedDateTime%20DESC`

#### Procore (Production Environment)

Step	Field	Example Value	Notes
Connect to your HTTP Account	Connection Display Name	`Procore Demo Org`
	Authorization Type	`OAuth 2.0 Authorization Code`	The value in this field is fixed.
	Base URL	`https://api.procore.com`
	Client ID	`43a4c94b7e225ad7a8d99cb4a0ae0de26efa298…`
	Client Secret	`e84ee4db2f944a7b585ca110ac20793b5e6c0…`
	Authorization URL	`https://login.procore.com/oauth/authorize`
	Token Exchange URL	`https://login.procore.com/oauth/token`
	Token Refresh URL	`https://login.procore.com/oauth/token`
	Token Revoke URL	`https://login.procore.com/oauth/revoke`
	Access Token Expired Code	`401`
Test HTTP Connection	Request Method	`Get`
Test HTTP Connection	Request Path	`/rest/v1.0/me`

#### Procore (Sandbox Environment)

Step	Field	Example Value	Notes
Connect to your HTTP Account	Connection Display Name	`Procore Sandbox Demo Org`
	Authorization Type	`OAuth 2.0 Authorization Code`	The value in this field is fixed.
	Base URL	`https://sandbox.procore.com`
	Client ID	`43a4c94b7e225ad7a8d99cb4a0ae0de26efa298…`
	Client Secret	`e84ee4db2f944a7b585ca110ac20793b5e6c0…`
	Authorization URL	`https://login-sandbox.procore.com/oauth/authorize`
	Token Exchange URL	`https://login-sandbox.procore.com/oauth/token`
	Token Refresh URL	`https://login-sandbox.procore.com/oauth/token`
	Token Revoke URL	`https://login-sandbox.procore.com/oauth/revoke`
	Access Token Expired Code	`401`
Test HTTP Connection	Request Method	`Get`
Test HTTP Connection	Request Path	`/rest/v1.0/me`

#### QuickBooks > [!NOTE] Add the `Accept: application/json` HTTP header to your requests since QuickBooks returns > HTML by default.

Step	Field	Example Value	Notes
Connect to your HTTP Account	Connection Display Name	`My QuickBooks connection`
	Authorization Type	`OAuth 2.0 Authorization Code`	The value in this field is fixed.
	Base URL	`https://sandbox-quickbooks.api.intuit.com`	In your QuickBooks account, check for the realm ID or company ID. For example: `4620816365253449610`.
	Client ID	`ABOCnl9CHHDDpZ0RASkhadwSVBa1…`
	Client Secret	`qwDPs7K1huLWn2ZfdeVHQgpyYr…`
	Scopes	`com.intuit.quickbooks.accounting`	For more information about scopes, check your QuickBooks account. When you create your QuickBooks account, you have two scopes depending on the URLs you need to use.
	Authorization URL	`https://appcenter.intuit.com/connect/oauth2`	You must register your callback URL in your QuickBooks account in your application configuration. QuickBooks allows you to register multiple callback URLs, so you can create one application for all your environments.
	Token Exchange URL	`https://oauth.platform.intuit.com/oauth2/v1/tokens/bearer`
	Token Exchange Headers	Parameter 1: Key Value
	Token Refresh URL	`https://oauth.platform.intuit.com/oauth2/v1/tokens/bearer`
	Token Refresh Headers	Parameter 1: Key Value
	Token Revoke URL	`https://developer.api.intuit.com/v2/oauth2/tokens/revoke`
	Token Revoke Headers	Parameter 1: Key Value
	Access Token Expired Code	`401`
Test HTTP Connection	Request Method	`Get`
Test HTTP Connection	Request Path	`/v3/company/{realmId}/companyinfo/{realmId}`

#### Salesforce

Step	Field	Example Value	Notes
Connect to your HTTP Account	Connection Display Name	`My Salesforce Acme connection`	Including the Salesforce instance name in this field aids in identifying the connection from a list.
	Authorization Type	`OAuth 2.0 Authorization Code`	The value in this field is fixed.
	Base URL	`https://<instance>.my.salesforce.com`
	Client ID	`3MVG9kBt168mda_.aAARdkSYhzS6mkIA5bVzvid_ppcSV44vtKUFV3J`	The value in this field is the Salesforce Connected App Client ID.
	Client Secret	`620187E2CD2DAEF6725AA404EADDFD8FECB390FA854DB637B95E186`	The value in this field is the Salesforce Connected App Secret.
	Scopes	`full refresh_token`
	Authorization URL	`https://login.salesforce.com/services/oauth2/authorize`
	Authorization URL Query Parameters	Key: `prompt` Value: `login consent`
	Token Exchange URL	`https://login.salesforce.com/services/oauth2/token`
	Token Refresh URL	`https://login.salesforce.com/services/oauth2/token`
	Token Revoke URL	`https://login.salesforce.com/services/oauth2/revoke`
	Access Token Expired Code	`401`
Test HTTP Connection	Request Method	`Get`
Test HTTP Connection	Request Path	`/services/data/v55.0/`	For more information, see the Salesforce REST API Developer Guide documentation.

#### Shopify

Step	Field	Example Value	Notes
Connect to your HTTP Account	Connection Display Name	`Shopify at my.account@example.com (QA)`	For more information, see the Shopify Partner Program.
	Authorization Type	`OAuth 2.0 Authorization Code`	The value in this field is fixed.
	Base URL	`https://myowndevelopmentstore1.myshopify.com`
	Client ID	`04bad9ea727686d3a61a47cc23772587`
	Client Secret	`668ca7383d2558aa9f4270550a4dff62`
	Scopes	`write_customers` `write_orders` `write_products`
	Authorization Headers	Authorization Header Name: `X-Shopify-Access-Token` Authorization Header Value Prefix: `Bearer Prefix` Authorization Header Custom Value Prefix: None
	Token Exchange URL	`https://myowndevelopmentstore1.myshopify.com/admin/oauth/access_token`
	Access Token Expired Code	`401`
Test HTTP Connection	Request Method	`Get`
Test HTTP Connection	Request Path	`/admin/api/2022-07/shop.json`

#### Slack

Step	Field	Example Value	Notes
Connect to your HTTP Account	Connection Display Name	`My Slack inspiration workspace connection`	Including the Slack workspace name aids in identifying the connection from a list.
	Authorization Type	`OAuth 2.0 Authorization Code`	The value in this field is fixed.
	Base URL	`https://<my-workspace>.slack.com`
	Client ID	`3806739369586.3819433415633`	`The value in this field is the Slack App Client ID.`
	Client Secret	`d1cc08d9b2bf8573fa10e43f458d51a9`	`The value in this field is the Slack App Secret.`
	Scopes	`chat:write`
	Authorization URL	`https://slack.com/oauth/v2/authorize`
	Token Exchange URL	`https://slack.com/api/oauth.v2.access`
	Token Refresh URL		Leave the value in this field blank.
	Token Revoke URL	`https://slack.com/api/auth.revoke`
	Access Token Expired Code	`401`
Test HTTP Connection	Request Method	`Get`
Test HTTP Connection	Request Path	`/api/api.test`

#### Xero

Step	Field	Example Value	Notes
Connect to your HTTP Account	Connection Display Name	`Xero Demo Company (US) connection`
	Authorization Type	`OAuth 2.0 Authorization Code`	The value in this field is fixed.
	Base URL	`https://api.xero.com/`
	Client ID	`1AAE161E43B448C2A17B59`
	Client Secret	`aMLNRJr3-oAaFtQOx1B-uf19qT`
	Scopes	`offline_access` `openid` `profile` `email` `accounting.transactions` `accounting.attachments` `accounting.reports.read` `accounting.settings` `accounting.contacts` `accounting.journals.read`	For more information, see the Xero Developer documentation.
	Authorization URL	`https://login.xero.com/identity/connect/authorize`
	Token Exchange URL	`https://identity.xero.com/connect/token`
	Token Refresh URL	`https://identity.xero.com/connect/token`
	Token Revoke URL	`https://identity.xero.com/connect/revocation`
	Access Token Expired Code	`401`
Test HTTP Connection	Request Method	`Get`
	Request Path	`/api.xro/2.0/Users`	For more information, see the Xero documentation: OAuth 2.0 for Xero Standard authorization code flow for Xero
	Request Path Headers	Key: `Xero-Tenant-Id` Value: `4268faf8-82a2-44e2-8ea2-4ec8f6ea3a26`	For more information, see the following: Xero login Standard authorization code flow for Xero

#### Configure an OAuth 2.0 Authorization Code Connection When creating an OAuth 2.0 Authorization Code connection with HTTP Connector, you must provide additional information to establish the connection. To establish an OAuth 2.0 Connection: 1. Open a flow or create a new flow. 2. Select a trigger or use the scheduler. 3. Click or create an HTTP connection for the action. 4. In the **Connect to your HTTP Account** window, in the **Authorization Type** field, select **OAuth 2.0 Authorization Code** and provide values for the following fields: 1. **Authorization URL**: The URL that starts the OAuth 2.0 flow. 2. **Authorization URL Query Parameters**: The key-value pairs that appear after the question mark in the URL. Under the OAuth Authorization Code Grant type, the authorization request sends data as query parameters. Composer handles these query parameters automatically, but sometimes additional parameters are useful. For example, the Google API needs `access_token=offline` to emit a refresh token. Without this parameter, a connection will expire after an hour. 3. **Token Exchange URL**: The URL where the authorization code can be exchanged for an access token. - Optionally, if you click **Add Headers**, provide a value for the following fields: - **Key** - **Value** 4. **Token Refresh URL (Optional)**: The URL where the token can be refreshed. This field is applicable only if the application marks the tokens as expired after a certain period of time. - Optionally, if you click **Add Headers**, provide a value for the following fields: - **Key** - **Value** 5. **Token Revoke URL (Optional)**: The URL where the token can be revoked or removed. - Optionally, if you click **Add Headers**, provide a value for the following fields: - **Key** - **Value** 5. Click **Next**. The OAuth 2.0 Authorization Code Connection is configured. You can now test the connection. ### Test the Connection After you establish a connection method, you can test the connection. While Composer tests other connectors automatically in the background, you must test HTTP Connector. You can decide which page to use for the test. Testing the connection is important because you cannot edit the connection later. To test the connection, provide a value for the following fields: - **Request Method** - **Request Path**: The value in this field is relative to the Base URL. - **Request Headers** - **Key** - **Value** - **Request Body**: This option appears when the HTTP method is POST and is the body of the request message. Click **Connect** to test the connection. A message appears to indicate the connection was created successfully (indicated by a response code of `200`) or that an error occurred. Note that if the application requires a token exchange to transact data, you need to create a token for each use case. For example, in Salesforce Marketing Cloud, this is needed because the first step in Flow 1 will generate a token, which might get invalidated by a similar step in Flow 2. ## HTTP Connector Fields The following fields are applicable for HTTP Connector:

Name	Type	Description
Relative URL	String	URL for the target of the request without considering the base path.
Action	String	The type of request. You must choose between Request or Paginated Request.
HTTP Method	String	The HTTP method for the request. The following HTTP methods are available: GET: Retrieves information from the server. POST: Sends information to the server. PUT: Updates information in existing records on the server. PATCH: Updates specific data for existing records on the server. DELETE: Deletes information in existing records on the server.
Path	String	Identifies the specific resource in the server that you want to access.
Headers	Object	Allows you and the server to pass additional information with an HTTP request or response. Consists of its case-insensitive name (key) followed by a colon, and then followed by its value. If you add headers, you must provide values for the Key and Value fields. If you specify a POST, PUT, PATCH, or DELETE method and you add a request body, you must add the Content-Type: application/json header. Check the connected API for the desired field name for the Content-Type: application/json header since some APIs require different names for this header. If the header is Content-Type: application/json, then the minimum valid JSON ({}, "") is required as part of the request body. Note that [] is not supported at the root of the request body.
Query Parameters	Object	Query parameters to include in the request. If you add query parameters, you must provide values for the Key and Value fields.
Example Request	String	An example request in JSON format. If you provide a value for this field, Composer parses the example to deduce its fields. The fields are then available for entering data to configure the request operation. To view the fields Composer deduced from the example, click Select Additional Fields. The example JSON value provided in this field must be different than the value provided in the Example Response field.
Example Response	String	An example response in JSON format. If you provide a value for this field, Composer parses the example JSON payload and provides data pills that match the JSON fields.
Array Path	String	The path to the JSON array. The value from the Array Path field is selected by default, but a different value can be selected from the dropdown. This value only appears if the value in the Action field is set to Paginated Request.
Pagination Type	String	The type of pagination for the request. The following Pagination Types are available: Link Header: If this value is selected, provide a value in the Link Relation field. Marker: If this value is selected, provide a value in the following fields: Marker Parameter Name Next Marker Expression Next URL: If this value is selected, provide a value in the Next URL Expression field. Offset: If this value is selected, provide a value in the Offset Parameter Name field. Page Number: If this value is selected, provide a value in provide a value in the Page Number Parameter Name field.
Maximum Number of Pages	Number	The maximum number of pages returned from the API in requests.

## Actions After you connect to a system and define the trigger or configure a scheduler, you define the actions that the flow performs. For example, you can copy a record between different systems, such as Workday and Salesforce. The actions you can perform depend on which system you are connected to. This system provides the following actions: Request in HTTP When **Request** is selected in the **Action** field, a request in HTTP returns the fields of the response payload. A value is required for the following fields: - **Action** - **HTTP Method** - **Path** - **Example Response** - Optionally, if you click **Add Query Parameters**, provide a value for the following fields: - **Key** - **Value** - Optionally, if you click **Add Headers**, provide a value for the following fields: - **Key** - **Value** Paginated Request in HTTP When **Paginated Request** is selected in the **Action** field, a paginated HTTP request is initiated. A Paginated Request returns a list of items that subsequent flow steps can use in a For Each Loop. Composer automatically uses the pagination configuration to fetch data from the API. A value is required for the following fields: - **Action** - **HTTP Method** - **Path** - **Example Response** - **Array Path** - **Pagination Type** - Optionally, if you click **Add Query Parameters**, provide a value for the following fields: - **Key** - **Value** - Optionally, if you click **Add Headers**, provide a value for the following fields: - **Key** - **Value** ## See Also - [Mulesoft Composer: Overview](https://docs.mulesoft.com/composer/ms_composer_overview) - [MuleSoft Composer: Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) - [Composer Connector Reference](https://docs.mulesoft.com/composer/ms_composer_reference) - [Knowledge Articles](https://help.salesforce.com/s/) --- product: Composer --- # HubSpot Connector Reference > For the full documentation index, see: https://docs.mulesoft.com/llms.txt HubSpot offers a full platform of marketing, sales, customer service, and CRM software, as well as methodology, resources, and support, to help businesses grow. > [!NOTE] You can sync to HubSpot Company and Contact objects only. ## Connections To connect to a system, whether it is a source of data or the target where you are sending data, you must create a connection with that system’s required credentials. You typically connect to different systems within a flow and can reuse each connection every time you need to connect. This system requires the following credential information for its connections: Connection Display Name Enter a connection name that will help you remember the details of this connection. You can reuse connections multiple times in a single flow, and in more than one flow, and the credentials are hidden after you create the connection. Therefore, it’s helpful to provide a name that easily identifies this connection from others. Only you can see the connection. Other users in your Composer app must create their own connections. Bearer token The HubSpot account access token. ## Triggers Each flow starts with either a _scheduler_ or a _trigger_. Schedulers are set to a default frequency of 15 minutes. Triggers, such as "each time a new record is created", are defined by you and provide multiple options related to the data in your system. Triggers use a polling process to actively check for new updates from an external system. The polling frequency is 15 seconds. This system provides the following trigger options: On New Record Triggers when a new Company or Contact record is created. On New or Updated Record Triggers when a new Company or Contact record is created or updated. ### Polling Frequency For triggers in this connector, the **Polling Frequency** field is required. This field enables you to select how often Composer makes a request to the underling system API to look for changes to records in active flows. You can select a different polling frequency for each flow in your organization. With a shorter frequency, the flow executes more often; however, a shorter frequency consumes more [API calls](https://docs.mulesoft.com/general/automation-credits-usage-and-rates). For example, if you have an order management flow, you might require nearly real-time updates, which can be achieved with a 15-second polling interval (which equates to 5760 API calls per day). In contrast, if your flow updates a pricing catalog, you could poll the flow every hour (which equates to 24 API calls per day). ## Actions After you connect to a system and define the trigger or configure a scheduler, you define the actions that the flow performs. For example, you can copy a record between different systems, such as Workday and Salesforce. The actions you can perform depend on which system you are connected to. This system provides the following actions: Create new record Create a company or a contact in HubSpot. To create a new company, provide a value for **Company Name**. To create a new contact, provide a value for **Contact Name**. Update a record Update a company or a contact in HubSpot as specified by an external ID. To update a company or a contact, provide a value for **HubSpot ID**. Create or update record Create or update a company or a contact in HubSpot in a single step. To create or update a company, provide a value for **HubSpot ID**. To create or update a contact, provide a value for **External ID Field to Match**. ## See Also - [Mulesoft Composer: Overview](https://docs.mulesoft.com/composer/ms_composer_overview) - [MuleSoft Composer: Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) - [Composer Connector Reference](https://docs.mulesoft.com/composer/ms_composer_reference) - [Knowledge Articles](https://help.salesforce.com/s/) --- product: Composer --- # Invoking a Composer Flow > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Invoke a Composer flow from external systems to enable deeper interoperability and integrated capabilities across Salesforce. You can also authenticate every invocable flow for a secure and protected automation experience, create API-compatible invocable actions for seamless integration with diverse systems and applications, and build powerful automations by leveraging the built-in support for input and output fields. When your invocable flow is activated, Composer exposes a unique flow URL and a unique pair of client credentials (client ID and client secret) so that your flow can be invoked from external systems. You can reset these credentials for security best practices. Invoke invocable flows by using an HTTP call to the flow URL and using the flow client credentials as authentication. To invoke a Composer flow: 1. [Create an invocable Composer flow.](#create-an-invocable-composer-flow) 2. [Invoke the Composer flow from an external system.](#invoke-the-composer-flow-from-an-external-system) ## Create an Invocable Composer Flow Create an invocable Composer flow so that you can invoke it later from an external system: 1. [Configure your invocable Composer flow.](#configure-your-invocable-composer-flow) 2. [Test your invocable Composer flow.](#test-your-invocable-composer-flow) 3. [Activate your invocable Composer flow.](#activate-your-invocable-composer-flow) ### Configure Your Invocable Composer Flow To configure an invocable Composer flow: 1. Access Composer. 2. [Create a new flow from scratch](https://docs.mulesoft.com/composer/ms_composer_using_a_flow_and_creating_trigger#create-a-flow). 3. In the **What Should Start This Flow?** dialog, in the **Interaction** section, click **Invoke** to create an invocable flow. The **Trigger: Invoke this flow from an external system via HTTP POST Request** trigger appears. 4. Optionally, add input fields. For example, you can add an `Opportunity ID` input field that returns a value if Salesforce passes the value of an opportunity ID to the Composer flow. To add input fields, click **Add Input Fields**. You can define input fields by using the **Visual Editor** or **Sample JSON Editor**. - To define input fields using the **Visual Editor**: 1. In the **Input Name** field, enter a unique name for the input field. The name must begin with a letter and cannot contain spaces. 2. In the **Data Type** dropdown, select the data type you want to use for the input field. The following [data types](https://docs.mulesoft.com/composer/ms_composer_custom_expression_editor#data-types) are supported: `String`, `Number`, `Boolean`, `Date`, and `DateTime`. 3. Optionally, add a value for **Sample Value** or **Help Text** to test the flow. 4. To add more input fields, click **Add Input**. 5. Click **Apply**. The count of input fields you added appears next to **Input Fields**, displaying one or more new input fields added to the flow. 6. Optionally, to change the input fields, click **Add Input Fields** to open the **Visual Editor**. - To define input fields by using the Sample **JSON Editor**: 1. In the **Example Request** window, paste or enter the JSON sample. Example: JSON sample in the **Sample JSON Editor** window ```JSON { { "name": "ben", "age": 100 } } ``` Unlike the **Visual Editor**, the **Sample JSON Editor** supports objects, arrays, and null values. Example: Complex JSON sample in the **Sample JSON Editor** window ```JSON { "data": { "favoriteNumbers": [3, 7, 13, 17, 23] } } ``` 2. Click **Apply**. The count of the of input fields you added appears next to **Input Fields**, displaying one or more new input fields added to the flow. 3. Optionally, to change the input fields, click **Add Input Fields** to open the **Sample JSON Editor** to edit the input fields. 5. Optionally, add output fields. If specified, output fields are returned as the JSON response. For example, if there is an `Opportunity ID` input field, you can add the value of the ID as an output field, in which the following JSON response is returned with a 200 status code: ```JSON { "opportunityId": "" } ``` To add output fields: 1. Click **Add Output Fields**. 2. In the **Label** field, enter a unique name for the output field. The name must begin with a letter. Avoid including spaces in this field since spaces are escaped and replaced with x20. 3. In the **Data Type** dropdown, select the data type you want to use for the output field. The following [data types](https://docs.mulesoft.com/composer/ms_composer_custom_expression_editor#data-types) are supported: `String`, `Number`, `Boolean`, `Date`, and `DateTime`. If you select **List**, in the **List Item Type** field, select: - **String**, **Number**, or **Boolean** to return a list that contains primitive data types - **Object** to return a list of objects, for example, the output of the **Get Records** action 4. Click **Apply**. 5. Once output fields are added, you can then map data pills, custom expressions, or plain text. For example, map an input field to the output field. - `String`, `Number`, `Boolean`, `Date`, or `DateTime`, a value is required. You can enter a value manually, select any existing data pill (including variables) from your flow, select a [Picklist Mapping](https://docs.mulesoft.com/composer/ms_composer_using_actions_in_a_flow#create-a-picklist-mapping) (for `String` variables) or you can select the [**Custom Expression Editor**](https://docs.mulesoft.com/composer/ms_composer_custom_expression_editor#add-custom-expression-to-an-action) to create a custom expression. - `List`, a value is required. You can enter a value manually. For primitive list types (`String`, `Number`, `Boolean`, `Date`, or `DateTime`), you can create a list statically using the [**Custom Expression Editor**](https://docs.mulesoft.com/composer/ms_composer_custom_expression_editor#add-custom-expression-to-an-action) or [map in a list data pill](https://docs.mulesoft.com/composer/ms_composer_using_actions_in_a_flow#create-a-picklist-mapping). For List, select either: - **Dynamic List** to create multiple items in the list. Use a list pill to reference the number of items created. Then, map the fields of the elements of the list. - **Static List**, and then initialize the list with as many items as you need. If you do not add any items, the list is empty by default. 6. Optionally to change the output fields, click **Add Output Fields** to open the editor to edit the output fields. 6. Complete the flow. For example, configure system actions for the flow, define variables, or create flow controls as described in [Configuring and Managing Flows](https://docs.mulesoft.com/composer/ms_composer_flows). 7. Click **Save**. To delete an invocable step from your flow: 1. Access the flow that contains the invocable flow step to delete. 2. In the corner of the step, click **…** > **Delete step**. ### Test Your Invocable Composer Flow To test your invocable Composer flow: 1. In your invocable flow, click **Test**. If you added input fields, the **Test Flow** window appears. 2. Enter a sample value for the input field or review the complex JSON to test the flow. 3. Click **Test Flow**. The testing output appears. Using this output, you can verify if the flow returns the expected values in the sample output of the main canvas. ### Activate Your Invocable Composer Flow To activate your invocable Composer flow: 1. In your invocable flow, click **Activate**. The flow details page appears with a message indicating that the flow is now active. When an invocable flow is activated for the first time, the org admin receives an email. 2. Click **Flow Credentials** to view the flow data that invokes the flow from the external system. If your flow is deactivated for more than 30 days, the flow credentials will expire. New flow credentials are generated the next time your flow is activated. 3. You can reset the flow credentials periodically to ensure continuous security. In the **Flow Credentials** window, click **Reset Client Secret**. The **Client Secret** field is updated. Click the clipboard icon next to the field to copy the new **Client Secret** value. Once the client secret is reset, the previous client secret no longer works. You must manually share the new client secret to external systems that invoke this Composer flow. 4. Ensure the following fields have values: - **URL**: Unique URL of the flow you are invoking. - **Client ID**: Username or unique identifier to authenticate this flow. - **Client Secret**: Password or secret to authenticate this flow. - **OpenAPI Specification**: OpenAPI specification that describes the structure of the underlying API of this flow. 5. Click **Close**. ## Invoke the Composer Flow from an External System After creating an invocable flow in Composer, you can invoke it from an external system: - [Invoke a Composer Flow from Flow Builder](#invoke-a-composer-flow-from-flow-builder) - [Invoke a Composer Flow from Flow Orchestration](#invoke-a-composer-flow-from-flow-orchestration) - [Invoke a Composer Flow from Another Composer Flow](#invoke-a-composer-flow-from-another-composer-flow) - [Invoke a Composer Flow from an Apex Callout](#invoke-a-composer-flow-from-an-apex-callout) - [Invoke a Composer Flow from a cURL Command](#invoke-a-composer-flow-from-a-curl-command) ### Invoke a Composer Flow from Flow Builder Invoke a Composer flow directly from Flow Builder to build integrations without writing a single line of code. For example, use invocable flows to build integrations in Flow Builder that connect to third-party systems such as NetSuite, Jira, and Workday. Some use cases include using Flow Builder to call an invocable Composer flow that: - Creates a Jira issue when a record is created in Salesforce. - Retrieves an order status from NetSuite and posts a message in Slack. - Gets real-time credit scores when a user goes through a screen flow. - Retrieves an order status from NetSuite when a user enters an order ID in the screen flow. To invoke a Composer flow from Flow Builder: 1. [Set up Salesforce for invocable flows](#set-up-salesforce-for-invocable-flows). 2. [Set up Flow Builder for invocable flows](#set-up-flow-builder-for-invocable-flows). #### Set Up Salesforce for Invocable Flows After creating your Composer flow, set up your Salesforce org to invoke flows in Composer: 1. Access your Salesforce org. 2. Create a new set of credentials that use the same credentials that you use for Composer. Create an external credential and a named credential. If your invocable Composer flow does not contain input fields, add a new `Content-Length` custom header that has a value of `0` in the external credential and named credential to avoid an HTTP 411 response. To create an external credential and a named credential: 1. [Create and edit a custom authentication external credential](https://help.salesforce.com/s/articleView?id=xcloud.nc_create_edit_custom_auth_ext_cred.htm&type=5). 2. [Enable external credential principals](https://help.salesforce.com/s/articleView?id=xcloud.nc_enable_ext_cred_principal.htm&type=5). 3. [Use basic authentication with named credentials](https://help.salesforce.com/s/articleView?id=xcloud.nc_custom_headers_basic_auth.htm&type=5). 4. [Create and edit a named credential](https://help.salesforce.com/s/articleView?id=xcloud.nc_create_edit_named_credential.htm&type=5). 3. Register your external service by copying the API specification from the Composer flow as described in [Paste the JSON-formatted Schema Into Your Browser](https://help.salesforce.com/s/articleView?id=platform.external_services_register_json.htm&type=5). #### Set Up Flow Builder for Invocable Flows After setting up Salesforce for invocable flows, you can call the Composer flow from Flow Builder: 1. Access your Salesforce org. 2. Go to **Setup** > **Process Automation** > **Flows**. 3. Click **New Flow** to create a new flow in Flow Builder. 4. Select the type of flow you want to create, for example, a **Record-Triggered Flow**, and then click **Create**. 5. Configure the start of the flow. If you create a record-triggered flow, select **Run Asynchronously** to avoid errors. 6. Set up an invocable action. Click **+** to add a new element and then click **Action**. 7. In **Filter By**, select **Type** and click **External Service**. 8. Select the action of the invocable flow from the external service. 9. Enter a value for the **Label** and **API Name** fields. 10. If you are invoking a Composer flow with inputs, follow these steps: In **Set Input Values**, for **body**, set the input value to the external service that triggers the Composer flow. To set the input value, click **New Resource** and ensure the following fields have values: - **Resource Type**: Select a resource type. - **API Name**: Enter a name for the API. - **Data Type**: Select a data type. - **Apex Class**: Search for an Apex class. - **Availability Outside the Flow**: Select **Available for input** and **Available for output** if needed. For example, if Salesforce passes the value of an opportunity ID to the Composer flow, the values are: - **Resource Type**: `Variable` - **API Name**: `InvocableFlowInputPayload` - **Data Type**: `Apex-Defined` - **Apex Class**: `ExternalService__InvocableFlowTest_invoke_IN_body` - **Availability Outside the Flow**: **Available for input** and **Available for output** 11. Click **Done**. The invocable action is set up. 12. Click **Done**. 13. Add an assignment by clicking **+** above the action to add a new element and then click **Assignment**. 14. Enter a **Label** and **API Name**. 15. Set variable values: - **Variable**: Enter the **API Name** of the new resource from step 10. - **Operator**: Select the operator to indicate or change the value. - **Value**: The value is assigned to the input fields when creating the invocable flow. For example, to set a value from a Salesforce record to an opportunity ID variable, the values are: - **Variable**: `{!InvocableFlowInputPayload.opportunityId}` - **Operator**: `equals` - **Value**: `{!$Record.id}` 16. If you are invoking a Composer flow with outputs, you can use the invocable flow output in your Salesforce flow. For example, if your invocable flow returns an opportunity ID, you can use the **Update Records** flow element to assign this opportunity ID to any record field. In the **Set Field Values for the Account Record** section, in the **Value** field dropdown, your invocable flow output is available by selecting the `Outputs from ActionName > 200 > [Available Output Values]` option, in which `ActionName` is the Label or API Name from step 9 and `Available Output Values` is the outputs from the flow, as interpreted from the API specification added in the external service. Then, in the **Field** field, you can select any field on the record that you want to update. 17. Save the flow. Enter a **Flow Label** and **Flow API Name**. 18. Click **Save**. 19. Debug the flow as described in [Debug a Flow in Flow Builder](https://help.salesforce.com/s/articleView?id=platform.flow_test_debug.htm&type=5). 20. Test the flow as described in [Test a Flow](https://help.salesforce.com/s/articleView?id=platform.flow_concepts_testing.htm&type=5). 21. Activate the flow as described in [Activate or Deactivate a Flow](https://help.salesforce.com/s/articleView?id=platform.flow_distribute_activate.htm&type=5). ### Invoke a Composer Flow from Flow Orchestration Use Flow Orchestration to create complex multi-step processes. Invoke a Composer flow in Flow Orchestration to enhance workflow automation and increase scalability. To invoke a Composer flow from Flow Orchestration: 1. [Set up Salesforce for invocable flows](#set-up-salesforce-for-invocable-flows-orch). 2. [Set up Flow Orchestration for invocable flows](#set-up-flow-orchestration-for-invocable-flows). #### Set Up Salesforce for Invocable Flows After creating your Composer flow, set up your Salesforce org to invoke flows in Composer: 1. Access your Salesforce org. 2. Create a new set of credentials that use the same credentials that you use for Composer. Create an external credential and a named credential. If your invocable Composer flow does not contain input fields, add a new `Content-Length` custom header that has a value of `0` in the external credential and named credential to avoid an HTTP 411 response. To create an external credential and a named credential: 1. [Create and edit a custom authentication external credential](https://help.salesforce.com/s/articleView?id=xcloud.nc_create_edit_custom_auth_ext_cred.htm&type=5). 2. [Enable external credential principals](https://help.salesforce.com/s/articleView?id=xcloud.nc_enable_ext_cred_principal.htm&type=5). 3. [Use basic authentication with named credentials](https://help.salesforce.com/s/articleView?id=xcloud.nc_custom_headers_basic_auth.htm&type=5). 4. [Create and edit a named credential](https://help.salesforce.com/s/articleView?id=xcloud.nc_create_edit_named_credential.htm&type=5). Note that you must add the **Automated Process** user to the **Permission Sets** assignments. For more information, refer to [Assign a Permission Set to Multiple Users](https://help.salesforce.com/s/articleView?id=platform.perm_sets_manage_assignments.htm&type=5). 3. Register your external service by copying the API specification from the Composer flow as described in [Paste the JSON-formatted Schema Into Your Browser](https://help.salesforce.com/s/articleView?id=platform.external_services_register_json.htm&type=5). #### Set Up Flow Orchestration for Invocable Flows After setting up Salesforce for invocable flows, you can call the Composer flow from Flow Orchestration: 1. First, [set up Flow Builder for invocable flows](#set-up-flow-builder-for-invocable-flows) before setting up Flow Orchestration. 2. Click **New Flow** > **All + Templates** > **Flow Orchestration**. Select either **Autolaunched Orchestration (No Trigger)** or **Record-Triggered Orchestration** and click **Create**. 1. If you select **Record-Triggered Orchestration**, select the object, configure the trigger, and set entry conditions. Click **Save**. 3. Click **+** to add a new element and then click **Stage**. 4. Enter a value for the **Label** and **API Name** fields and select a condition. 5. Click **Add Step** and click **Background Step**. 6. Enter a value for the **Label** and **API Name** fields and select a condition and an action. 7. Select the **Contains external callouts or pause elements** checkbox. 8. Click **Save**. 9. Click **Activate**. ### Invoke a Composer Flow from Another Composer Flow You can create an invocable flow in Composer and invoke it from another Composer flow. To invoke a Composer flow from another Composer flow: 1. [Create a new flow from scratch](https://docs.mulesoft.com/composer/ms_composer_using_a_flow_and_creating_trigger#create-a-flow). 2. Click **+** > **System Event** and select **HTTP**. 3. Configure your HTTP connection. For more information, refer to HTTP Connector [Connections](https://docs.mulesoft.com/composer/ms_composer_http_reference#connections). Ensure that the following fields have these values: - **Authorization Type**: `Basic Authentication` - **Base URL**: URL of the invocable flow - **Username**: Client ID of the invocable flow - **Password**: Client secret of the invocable flow 4. Click **Next**. 5. Configure the fields to test your HTTP connection. For more information, refer to [Test the Connection](https://docs.mulesoft.com/composer/ms_composer_http_reference#test-the-connection). Ensure that the following fields have these values: - **Request Method**: `POST` - **Request Path**: `/` - **Request Headers** - **Key**: `Content-Type` - **Value**: `application/json` - **Request Body**: Input fields of the invocable flow 6. Click **Connect**. After the connection is created, a flow can invoke another invocable flow. ### Invoke a Composer Flow from an Apex Callout Invoke a Composer flow from Apex classes using an Apex callout. Calling a Composer flow from Apex enables more flexibility because you can call the Composer flow from a Salesforce trigger, an Apex job, an Apex controller, or a Lightning Web Component (via an Apex controller). Calling a Composer flow from a Salesforce trigger or an Apex controller is immediate, whereas calling a Composer flow as part of a flow or from an Apex job is asynchronous. To invoke a Composer flow from an Apex callout: 1. [Set up Salesforce for invocable flows](#set-up-salesforce-for-invocable-flows-apex). 2. [Use Apex classes to trigger invocable flows](#use-apex-classes-to-trigger-invocable-flows). #### Set Up Salesforce for Invocable Flows After creating your Composer flow, set up your Salesforce org to invoke flows in Composer: 1. Access your Salesforce org. 2. Create a new set of credentials that use the same credentials that you use for Composer. Create an external credential and a named credential. If your invocable Composer flow does not contain input fields, add a new `Content-Length` custom header that has a value of `0` in the external credential and named credential to avoid an HTTP 411 response. To create an external credential and a named credential: 1. [Create and edit a custom authentication external credential](https://help.salesforce.com/s/articleView?id=xcloud.nc_create_edit_custom_auth_ext_cred.htm&type=5). 2. [Enable external credential principals](https://help.salesforce.com/s/articleView?id=xcloud.nc_enable_ext_cred_principal.htm&type=5). 3. [Use basic authentication with named credentials](https://help.salesforce.com/s/articleView?id=xcloud.nc_custom_headers_basic_auth.htm&type=5). 4. [Create and edit a named credential](https://help.salesforce.com/s/articleView?id=xcloud.nc_create_edit_named_credential.htm&type=5). 3. Register your external service by copying the API specification from the Composer flow as described in [Paste the JSON-formatted Schema Into Your Browser](https://help.salesforce.com/s/articleView?id=platform.external_services_register_json.htm&type=5). #### Use Apex Classes to Trigger Invocable Flows After setting up Salesforce for invocable flows, you can call the Composer flow from Apex classes using an Apex callout: 1. Access your Salesforce org. 2. Go to **Setup** > **Custom Code** > **Apex Classes**. 3. When an external service is created using the API specification from the Composer flow, Salesforce creates some Apex classes automatically. For example, suppose there is an invocable Composer flow that creates a Google Calendar meeting every time an opportunity in Salesforce is updated. The following example is an Apex class that represents the calendar meeting request body: // \[SERVICE\] GcalComposer // \[OBJECT\] GcalComposer.invoke.IN.body global class GcalComposer\_invoke\_IN\_body { // \[PROPERTY\] summary @AuraEnabled global String summary {get; set{ this.summary = value; this.summary\_set = true; }} global Boolean summary\_set {get; set;} // \[PROPERTY\] description @AuraEnabled global String description {get; set{ this.description = value; this.description\_set = true; }} global Boolean description\_set {get; set;} } You can view all of the Apex classes created automatically by Salesforce under the **Apex Classes** section. The only additional step is to write Apex code to use the external service Apex classes created automatically by Salesforce. Continuing with the previous example, the following code calls out to the invocable flow to create the Google Calendar meeting: public class ComposerGcalFlow { @future(callout=true) public static void invokeComposerFlow(String summary, String description) { ExternalService.GcalComposer\_invoke\_IN\_body body = new ExternalService.GcalComposer\_invoke\_IN\_body(); body.summary = summary; body.description = description; ExternalService.GcalComposer.invoke\_Request request = new ExternalService.GcalComposer.invoke\_Request(); request.body = body; ExternalService.GcalComposer service = new ExternalService.GcalComposer(); ExternalService.GcalComposer.invoke\_Response response = service.invoke(request); } } The callout to the invocable flow code can be made from a Salesforce trigger. In the following example, the invocable Composer flow is called every time an opportunity is updated: trigger OpportunityUpdate on Opportunity (after update) { for (Opportunity opp: Trigger.New){ ComposerGcalFlow.invokeComposerFlow(‘Opportunity ‘ + opp.Name + ‘updated’,opp.description); } } For more information about Apex callout limits and limitations, refer to [Callout Limits and Limitations](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_callouts_timeouts.htm). For more information about Apex, refer to [Apex Developer Guide](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_dev_guide.htm). ### Invoke a Composer Flow from a cURL Command You can invoke a Composer flow through a cURL command. Because each invocable Composer flow generates a public URL, you can use the URL to invoke the flow from your terminal. Invoking a Composer flow from a cURL command is beneficial because cURL commands can be used in scripts or code to automate business cases. cURL commands are also generally easy to share, modify, and test. For example, suppose there is a flow that calculates some basic math and also returns a string. The flow takes three input values (`a`, `b`, and `Message`) and returns five output values (`Output caption`, `Quotient`, `Product`, `Difference`, and `Sum`). The following cURL command invokes the Composer flow, in which `` is the flow URL and `` is the Base64 encoding of the client ID concatenated with a colon followed by the client secret: curl "" -H "Authorization: Basic " -X POST --data ' { "a": 100, "b": 30, "Message": "Basic Math Ops" } ' -H "Content-Type: application/json" The example response is: ```JSON { "Output caption": "Basic Math Ops", "Quotient": 3.333333333333333333333333333333333, "Product": 3000, "Difference": 70, "Sum": 130 } ``` ## Publish the Flow to Salesforce or an Anypoint Organization After activating your flow, you can publish the flow to your Salesforce organization. You must have the [Automation Starter or Automation Advanced subscription package](https://docs.mulesoft.com/general/automation-credits-usage-and-rates) to use this service. ## Troubleshooting When an external system successfully invokes a Composer flow, an HTTP 200 response occurs. To troubleshoot invocable flows, become familiar with the information about interpreting commonly thrown exception messages. ### Missing Required Input Parameters If a Composer flow requires input fields and the external system does not pass these fields, an HTTP 400 response occurs. ### Invalid Credentials If a Composer flow has invalid credentials, an HTTP 401 response occurs. ## See Also - [Mulesoft Composer: Overview](https://docs.mulesoft.com/composer/ms_composer_overview) - [MuleSoft Composer: Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) - [Composer Connector Reference](https://docs.mulesoft.com/composer/ms_composer_reference) - [Knowledge Articles](https://help.salesforce.com/s/) - [Trail: Build Flows with Flow Builder](https://trailhead.salesforce.com/content/learn/trails/build-flows-with-flow-builder) --- product: Composer --- # Jira Connector Reference > For the full documentation index, see: https://docs.mulesoft.com/llms.txt MuleSoft Composer’s Jira Connector automates issue tracking and project management workflows between Jira and other systems. You can create, update, and retrieve Jira issues automatically, sync project data across applications, and streamline support case escalation. The connector supports both standard and custom fields, enabling comprehensive integration with your existing Jira projects and workflows. To use Jira Connector with Composer, you must have the _Administrator Jira_ global permission. ## Connections To connect to a system, whether it is a source of data or the target where you are sending data, you must create a connection with that system’s required credentials. You typically connect to different systems within a flow and can reuse each connection every time you need to connect. This system requires the following credential information for its connections: Connection Name Enter a connection name that will help you remember the details of this connection. You can reuse connections multiple times in a single flow, and in more than one flow, and the credentials are hidden after you create the connection. Therefore, it’s helpful to provide a name that easily identifies this connection from others. Only you can see the connection. Other users in your Composer app must create their own connections. Organization Site URL Enter the URL of the Jira organization containing the sandbox or production environment to which you want to connect. If you do not specify a value in the **Organization Site URL** field, the connection uses the first URL listed in the `/resources` endpoint of the Atlassian API. Set the **Organization Site URL** field for every connection if you want the connection to use a specific organization instead of a default organization. For more information about Jira organizations, see the [Jira documentation](https://support.atlassian.com/organization-administration/docs/get-started-with-an-atlassian-organization/). To connect to a Jira organization via an Atlassian account: 1. In the **Connect to your Jira Account** window, in the **Organization Site URL** field, enter the Jira organization URL. For example, `https://orgname.atlassian.net`. 2. Click **Connect**. An Atlassian window appears, indicating that Composer is requesting access to an Atlassian account. 3. In the window, in the **Authorize for site** dropdown, select the organization you want to use and then click **Accept**. Composer is now connected to your Jira organization. Username The OAuth username that you use to log in to Jira. Password The OAuth password that you use to log in to Jira. ## Triggers Each flow starts with either a _scheduler_ or a _trigger_. Schedulers are set to a default frequency of 15 minutes. Triggers, such as "each time a new record is created", are defined by you and provide multiple options related to the data in your system. Triggers use a polling process to actively check for new updates from an external system. The polling frequency is 15 seconds. This system provides the following trigger options: New issue with Custom Fields Checks for a new issue with Custom fields created in Jira. New issue with Standard Fields only Checks for a new issue with Standard fields created in Jira. Update issue with Custom Fields was updated or created Checks for updated or created issues with Custom fields in Jira. Update issue with Standard Fields only was updated or created Checks for updated or created issues with Standard fields in Jira. ### Polling Frequency For triggers in this connector, the **Polling Frequency** field is required. This field enables you to select how often Composer makes a request to the underling system API to look for changes to records in active flows. You can select a different polling frequency for each flow in your organization. With a shorter frequency, the flow executes more often; however, a shorter frequency consumes more [API calls](https://docs.mulesoft.com/general/automation-credits-usage-and-rates). For example, if you have an order management flow, you might require nearly real-time updates, which can be achieved with a 15-second polling interval (which equates to 5760 API calls per day). In contrast, if your flow updates a pricing catalog, you could poll the flow every hour (which equates to 24 API calls per day). ## Actions After you connect to a system and define the trigger or configure a scheduler, you define the actions that the flow performs. For example, you can copy a record between different systems, such as Workday and Salesforce. The actions you can perform depend on which system you are connected to. This system provides the following actions: Create issue with custom fields Creates a new issue within the selected project. Provide a value for the following fields: - **Project** - **Key** - **Summary** - **Type** - **Status** - **Priority** Update issue with custom fields Updates specified Custom field values. Provide a value for the following fields: - **Issue ID or Key** - **Notify Users** Update issue with standard fields only Updates specified Standard field values. Provide a value for the following fields: - **Issue ID or Key** - **Notify Users** Get issue Returns details for a specific issue. Provide a value for **Issue ID or Key**. Add comment to issue Creates and adds a comment to an existing issue. Provide a value for the following fields: - **Issue ID or Key** - **Comment Text** Create project Creates a new project based on a project type template in Jira. Provide a value for the following fields: - **Key** - **Name** - **Lead Account ID** - **Project Type Key**: The value in this field must begin with an uppercase letter followed by one or more uppercase letters or numbers. Get project Returns the project details in Jira. Provide a value for **Project ID** or **Key**. Retrieve project Retrieves the project details for an existing project in Jira. Provide a value for **Project ID** or **Key**. Retrieve attachments for an issue Returns all attachments for this issue. This returns the files' metadata but not the contents of the files. The files are ordered by the date that they were uploaded. Provide a value for **Project ID** or **Key**. Retrieve attachment Returns a URL redirect to the raw file for a specified file attachment. Provide a value for **Attachment ID**. Upload an attachment for an issue Uploads an attachment for a Jira issue. Provide a value for the following fields: - **Issue ID or Key** - **File Name** ## Custom Fields Using MuleSoft Composer, you can access Standard custom field values in Jira for actions and triggers that you set in the Jira issue. Custom fields containing the following list components are not currently supported: - Text fields (multi-line) - Labels - Checkboxes - Radio buttons - Select lists (multiple-choice) - Select lists (cascading) - User picker ## Standard Fields The following standard fields are not supported at this time: - **Affects version** - **Fix version** - **Environment** - **Component** ## See Also - [Mulesoft Composer: Overview](https://docs.mulesoft.com/composer/ms_composer_overview) - [MuleSoft Composer: Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) - [Composer Connector Reference](https://docs.mulesoft.com/composer/ms_composer_reference) - [Knowledge Articles](https://help.salesforce.com/s/) --- product: Composer --- # Known Issues and Limitations for MuleSoft Composer > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The following list displays known issues and limitations for MuleSoft Composer. The list is sorted by the date in which the known issue or limitation appeared. ## October 22, 2026 ### Composer Platform

Known Issue	Workaround	ID
When you test a flow, Composer tracks a limited number of tracking notifications for each flow execution (100 by default) to show step-by-step results. When a flow generates more notifications, Composer drops the oldest ones. As a result, early steps can appear blank or not executed even though they ran and produced data. Only the display is affected. Your flow logic runs, records are created, and the execution completes. Composer isn’t designed for complex or large automations. The limitation depends on the complexity of the processing logic, not the size of the data. For example, a flow with 100 steps isn’t recommended. Complex flows can result in partial debug messages, slow load times, and other performance problems.	If early steps in a large flow appear blank after you test it, verify the results directly, for example, by checking the records created or updated in the target system. Keep your flows smaller and more manageable. For use cases that require advanced or complex logic, consider Anypoint Code Builder.	W-24287812

Known Issue

Workaround

When you test a flow, Composer tracks a limited number of tracking notifications for each flow execution (100 by default) to show step-by-step results. When a flow generates more notifications, Composer drops the oldest ones. As a result, early steps can appear blank or not executed even though they ran and produced data.

Only the display is affected. Your flow logic runs, records are created, and the execution completes.

Composer isn’t designed for complex or large automations. The limitation depends on the complexity of the processing logic, not the size of the data. For example, a flow with 100 steps isn’t recommended. Complex flows can result in partial debug messages, slow load times, and other performance problems.

If early steps in a large flow appear blank after you test it, verify the results directly, for example, by checking the records created or updated in the target system.

Keep your flows smaller and more manageable. For use cases that require advanced or complex logic, consider Anypoint Code Builder.

W-24287812

## September 12, 2025 ### Composer Platform

Known Issue	Workaround	ID
Composer’s functionality may be subject to various limitations related to the external systems and their respective limits used in data retrieval. Composer is primarily intended for processing simpler and more lightweight datasets. It is important to understand that there is no single, rigid limit and that specific thresholds vary depending on each individual use case. For example, the following limits apply to Salesforce Connector.	For use cases requiring greater control, advanced logic, or larger datasets, users should consider Anypoint Code Builder.	W-19176552

## August 19, 2024 ### Salesforce

Known Issue	Workaround	ID
In Salesforce Connector, the `SALESFORCE:CONNECTIVITY Failed to get next element` error is sometimes thrown when processing the next element of the loop.	Rerun the flow to catch the missed events. For more information, refer to the known issue.	W-16418279

## May 7, 2024 ### NetSuite

Known Issue	Workaround	ID
When selecting a record type, if there is a large amount of metadata, the metadata resolver cannot parse the data within the three-minute time limit required by Composer and the `Netsuite: Retrieving metadata for the step failed` error sometimes occurs.	For more information, see the knowledge article.	W-15586159

## October 31, 2023 ### Composer Platform

Known Issue	Workaround	ID
When testing an Invocable Flow, if the value in the output fields was generated by a custom expression or if the value is either a `List<Object>` or a `List<Primitive>` data type, then the flow’s final output step does not display the test output data. Output fields that refer to data pills or variables display test output as expected.	None	None

## May 31, 2023 ### SAP S/4HANA Cloud

Known Issue Workaround ID

Known Issue	Workaround	ID
When adding an action or a trigger, the Service field dropdown menu might appear empty, which prevents completing the connector configuration. Similarly, during configuration, the `Retrieving metadata for the step failed` error might occur.	This is an intermittent issue that should resolve after a brief period of time.	W-13527982

When adding an action or a trigger, the Service field dropdown menu might appear empty, which prevents completing the connector configuration.

Similarly, during configuration, the Retrieving metadata for the step failed error might occur.

This is an intermittent issue that should resolve after a brief period of time.

W-13527982

## March 22, 2023 ### Google BigQuery

Known Issue	Workaround	ID
Input parameter values of String or date data types must be provided between single quotes using the expression editor.	None	W-12696210

## August 3, 2022 ### RPA

Known Issue	Workaround	ID
If connecting to a different RPA than one for which that the existing flow was built, the current RPA process is not automatically mapped to the processes in the new org.	Complete the following steps: Delete the step in the flow. Re-add the step in the flow. Refresh the process list. Select the new process.	None
When getting a JSON from RPA, you can pass a list of objects to a connector supporting lists. For example, you can pass the list of order line items to NetSuite.	None	None
When getting a JSON from RPA, you cannot use primitive values of a list when iterating the list. For example, a list of strings can be iterated, but you cannot do anything with the resulting values.	None	None

## July 13, 2022 ### Composer Platform

Known Issue	Workaround	ID
When deleting a connection, Composer ensures that there are no flows using that connection. If there are flows using that connection, they appear in a list in the Delete Connection window. However, in rare cases, flows created or edited before July 12, 2022 might not appear in the list.

## April 29, 2022 ### Workday

Known Issue Workaround ID

Known Issue	Workaround	ID
In the Invoice object, all fields containing the data type `number` for amounts are sent as strings.	Using the Custom Expression Editor, you can use the typecasting function, `fromStringToNumber`, to change the field type from `string` to `number`. For example: `Unit Cost=fromStringToNumber(Sales Price)`

In the Invoice object, all fields containing the data type number for amounts are sent as strings.

Using the Custom Expression Editor, you can use the typecasting function, fromStringToNumber, to change the field type from string to number. For example:

Unit Cost=fromStringToNumber(Sales Price)

--- product: Composer --- # Marketo Connector Reference > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Marketo is marketing automation software that aids marketing practitioners, executives, and sales reps to score, nurture, and understand leads. Marketo empowers users with marketing automation, email marketing, lead management, and revenue attribution. ## Connections To connect to a system, whether it is a source of data or the target where you are sending data, you must create a connection with that system’s required credentials. You typically connect to different systems within a flow and can reuse each connection every time you need to connect. This system requires the following credential information for its connections: Connection Name Enter a connection name that will help you remember the details of this connection. You can reuse connections multiple times in a single flow, and in more than one flow, and the credentials are hidden after you create the connection. Therefore, it’s helpful to provide a name that easily identifies this connection from others. Only you can see the connection. Other users in your Composer app must create their own connections. Token URL The URL of the endpoint that provides the access token for Marketo. Client ID The OAuth Client ID that you use to log in to Marketo. Client Secret The OAuth Client Secret that you use to log into Marketo. REST API Endpoint The base URL of your Marketo instance. ## Triggers Each flow starts with either a _scheduler_ or a _trigger_. Schedulers are set to a default frequency of 15 minutes. Triggers, such as "each time a new record is created", are defined by you and provide multiple options related to the data in your system. Triggers use a polling process to actively check for new updates from an external system. The polling frequency is 15 seconds. This system provides the following trigger options: New Lead Returns a list of new lead activities after a given datetime. ### Polling Frequency For triggers in this connector, the **Polling Frequency** field is required. This field enables you to select how often Composer makes a request to the underling system API to look for changes to records in active flows. You can select a different polling frequency for each flow in your organization. With a shorter frequency, the flow executes more often; however, a shorter frequency consumes more [API calls](https://docs.mulesoft.com/general/automation-credits-usage-and-rates). For example, if you have an order management flow, you might require nearly real-time updates, which can be achieved with a 15-second polling interval (which equates to 5760 API calls per day). In contrast, if your flow updates a pricing catalog, you could poll the flow every hour (which equates to 24 API calls per day). ## Actions After you connect to a system and define the trigger or configure a scheduler, you define the actions that the flow performs. For example, you can copy a record between different systems, such as Workday and Salesforce. The actions you can perform depend on which system you are connected to. This system provides the following actions: Create Lead Creates a lead to the target audience. Provide a value for **Push Lead to Market to Request**. Update Lead Updates a lead to the target audience. Provide a value for **Push Lead to Market to Request**. Get/Find Lead Retrieves a single lead record through its Marketo ID. Add Lead to List Adds a Person record to a target static list. Update Lead Program Status Changes the program member status of a lead in a target program. Provide a value for **Change Lead Program Status Request**. Create Custom Object Create a custom object record for the target audience. Provide a value for **Sync Custom Object Request**. Update Custom Object Update a custom object record for the target audience. Provide a value for **Sync Custom Object Request**. ## See Also - [Mulesoft Composer: Overview](https://docs.mulesoft.com/composer/ms_composer_overview) - [MuleSoft Composer: Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) - [Composer Connector Reference](https://docs.mulesoft.com/composer/ms_composer_reference) - [Knowledge Articles](https://help.salesforce.com/s/) --- product: Composer --- # Microsoft Dynamics 365 Business Central Connector Reference > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Microsoft Dynamics 365 Business Central is an ERP tool that provides a consolidated way of managing sales, marketing, purchasing, inventory, manufacturing, and shipping logistics. Microsoft Dynamics 365 Business Central also contains a limited set of CRM tools for managing contacts, interactions, segments, opportunities, and marketing campaigns. ## Connections To connect to a system, whether it is a source of data or the target where you are sending data, you must create a connection with that system’s required credentials. You typically connect to different systems within a flow and can reuse each connection every time you need to connect. This system requires the following credential information for its connections: Connection Display Name Enter a connection name that will help you remember the details of this connection. You can reuse connections multiple times in a single flow, and in more than one flow, and the credentials are hidden after you create the connection. Therefore, it’s helpful to provide a name that easily identifies this connection from others. Only you can see the connection. Other users in your Composer app must create their own connections. You must disable the admin consent workflow because Composer does not support it. Base URI The parameter base URI, for example, `https://api.businesscentral.dynamics.com/v2.0///api/v2.0`. Each instance or tenant gets its own parameter base URI. Username The OAuth username that you use to log into Microsoft Dynamics 365 Business Central. Password The OAuth password that you use to log into Microsoft Dynamics 365 Business Central. ## Triggers Each flow starts with either a _scheduler_ or a _trigger_. Schedulers are set to a default frequency of 15 minutes. Triggers, such as "each time a new record is created", are defined by you and provide multiple options related to the data in your system. Triggers use a polling process to actively check for new updates from an external system. The polling frequency is 15 seconds. This system provides the following trigger options: On New or Updated Sales Order Checks for a new or updated sales order or a new or updated sales order line. Provide a value for **Company**. On New or Updated Item Checks for a new or updated item. Provide a value for **Company**. On New or Updated Customer Checks for a new or updated customer. Provide a value for **Company**. ### Polling Frequency For triggers in this connector, the **Polling Frequency** field is required. This field enables you to select how often Composer makes a request to the underling system API to look for changes to records in active flows. You can select a different polling frequency for each flow in your organization. With a shorter frequency, the flow executes more often; however, a shorter frequency consumes more [API calls](https://docs.mulesoft.com/general/automation-credits-usage-and-rates). For example, if you have an order management flow, you might require nearly real-time updates, which can be achieved with a 15-second polling interval (which equates to 5760 API calls per day). In contrast, if your flow updates a pricing catalog, you could poll the flow every hour (which equates to 24 API calls per day). ## Actions After you connect to a system and define the trigger or configure a scheduler, you define the actions that the flow performs. For example, you can copy a record between different systems, such as Workday and Salesforce. The actions you can perform depend on which system you are connected to. This system provides the following actions: Create Sales Order Create a single sales order and, if provided, a list of sales order lines. Provide a value for the following fields: - **Company** - **Customer Number** Update Sales Order Update a single sales order and, if provided, a list of sales order lines. Provide a value for the following fields: - **Company** - **Entity ID** - **ETag** Get Sales Orders Retrieve a filtered list of sales orders in addition to corresponding sales order lines. Provide a value for **Company**. Create Customer Create a single customer. Provide a value for **Company**. Update Customer Update a single customer. Provide a value for the following fields: - **Company** - **Entity ID** - **ETag** Get Customers Retrieve a filtered list of customers. Provide a value for **Company**. Create Item Create a single Item. Provide a value for **Company**. Update Item Update a single Item. Provide a value for the following fields: - **Company** - **Entity ID** - **ETag** Get Items Retrieve a filtered list of Items. Provide a value for **Company**. Create Item Variant Create a single Item Variant. Provide a value for the following fields: - **Company** - **Code** Update Item Variant Update a single Item Variant. Provide a value for the following fields: - **Company** - **Entity ID** - **ETag** Get Item Variants Retrieve a filtered list of Item Variants. Provide a value for **Company**. ## Custom Fields Custom fields are not supported. Using MuleSoft Composer, you can access standard field values for actions and triggers that you set in the Microsoft Dynamics 365 Business Central record. ## See Also - [Mulesoft Composer: Overview](https://docs.mulesoft.com/composer/ms_composer_overview) - [MuleSoft Composer: Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) - [Composer Connector Reference](https://docs.mulesoft.com/composer/ms_composer_reference) - [Knowledge Articles](https://help.salesforce.com/s/) --- product: Composer --- # Microsoft Teams Connector Reference > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Microsoft Teams is a SaaS enterprise communication system used to send messages within an organization and to customers outside of the direct organization. To send a Microsoft Teams message using MuleSoft Composer, you must have an active business, enterprise, or education Microsoft 365 license. ## Connections To connect to a system, whether it is a source of data or the target where you are sending data, you must create a connection with that system’s required credentials. You typically connect to different systems within a flow and can reuse each connection every time you need to connect. This system requires the following credential information for its connections: Connection Name Enter a connection name that will help you remember the details of this connection. You can reuse connections multiple times in a single flow, and in more than one flow, and the credentials are hidden after you create the connection. Therefore, it’s helpful to provide a name that easily identifies this connection from others. Only you can see the connection. Other users in your Composer app must create their own connections. You must disable the admin consent workflow because Composer does not support it. Username The username that you use to log in to Microsoft 365. Password The password that you use to log in to Microsoft 365. ## Actions After you connect to a system and define the trigger or configure a scheduler, you define the actions that the flow performs. For example, you can copy a record between different systems, such as Workday and Salesforce. The actions you can perform depend on which system you are connected to. This system provides the following actions: Send message to channel Sends a message to all users who are members of a specific Microsoft Teams channel. The following fields are required: - Team ID - Channel ID - Message ## See Also - [Mulesoft Composer: Overview](https://docs.mulesoft.com/composer/ms_composer_overview) - [MuleSoft Composer: Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) - [Composer Connector Reference](https://docs.mulesoft.com/composer/ms_composer_reference) - [Knowledge Articles](https://help.salesforce.com/s/) --- product: Composer --- # Monitoring a Composer Flow > For the full documentation index, see: https://docs.mulesoft.com/llms.txt After activation, you can monitor active Composer flows. 1. From the sidebar, click **Flows**. 2. Click the name of a flow to display the flow detail page. The flow detail page shows each time the flow runs and whether or not that run was successful. The run history is retained for a maximum of 14 days or 1000 records, whichever occurs first. ![Flow run history and other flow details in MuleSoft Composer](/mulesoft/current/en-us/composer/_images/images/success-monitoring-ms.png) ## See Also - [Mulesoft Composer: Overview](https://docs.mulesoft.com/composer/ms_composer_overview) - [MuleSoft Composer: Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) - [Composer Connector Reference](https://docs.mulesoft.com/composer/ms_composer_reference) - [Knowledge Articles](https://help.salesforce.com/s/) --- product: Composer --- # MuleSoft Composer Glossary > For the full documentation index, see: https://docs.mulesoft.com/llms.txt activate The process of starting a flow. clone The process of copying a flow, including all actions and triggers, in its entirety. Composer Task A Composer Task is any action executed on a Composer Connector, including but not limited to read, create, update, and delete. connection The credentials that give you access to a system where you want to access data: the username and password, and the URL where you enter them to gain access. Some systems require additional information such as a security token. copy The process of duplicating a portion of a flow. You can copy records, triggers, and actions. data pill A variable that allows you to reference a field name or other data structure from within a flow. data structure Structures that store data in a system. For example, Salesforce stores data in sObjects and fields, and Google Sheets stores information in sheets, rows, and cells. edit The process of modifying an existing flow, action, or trigger. for each A logic option that allows you to specify an action for each trigger criteria that is met. flow An automated process that connects to a system and then performs actions on data from that system: - **action**: Something you do with the data fetched from a connection, such as copying a record or row from one system to another. - **step**: A trigger, or one or more actions. Steps include the logic needed to decide whether to perform the step or skip it. A step optionally includes a connection different from the initial trigger. - **trigger**: The first step of every flow, a trigger is something that starts the automated process defined in a flow. A trigger is either an event such as "a new record is created," or a specified point in time. Time-based triggers are called schedulers. The first step of every flow is a trigger. if/else A logic option that allows you to set conditions and execute actions only when specific criteria are met. This enables you to create flows that cover more than one linear branch, without the need to create separate flows. logic The circumstances or requirements that must be met before an action is taken: if/else statements or for-each statements. Insert logic into steps as needed to ensure actions are taken only on the data that should be acted on, not on all the data returned. monitor The process of reviewing activated flows to ensure that they are running successfully. record A collection of fields and data types in Composer. A flow triggers either on a schedule or as a result of a change on a record. That record is then processed through each step in the flow. repair An action to refresh the access token to reconnect your OAuth connection. RPA API Calls Robotic Process Automation (RPA) API Call occur when a customer invokes an API to perform an operation, including, but not limited to lookup, validate, create, update, or delete data in a system as part of an RPA process. RPA Bot Minutes Robotic Process Automation (RPA) Bot Minutes are the number of minutes running process automations across all bot sessions. A single bot may run multiple parallel sessions, with RPA Bot Minutes counting for each parallel session. Multiple bots may be configured to run the same process, with RPA Bot Minutes counting for each of these separate bot sessions. Test runs or process runs in the test phase are also counted towards RPA Bot Minutes. schedule The process of automating the start of a flow at regular intervals. scheduler The mechanism by which flows are scheduled. system Composer connects to systems such as Salesforce, NetSuite, and Google Sheets to execute automated processes which you build, test, and activate as flows. Connections to a system can be made during any step in a flow. Flows must connect to a system during the first step, the trigger or scheduler, even if that system is the same Salesforce org where Composer is hosted. task A change made by Composer for Salesforce to an object or record in the target system(s) of an integration flow that is an insertion, update, or deletion. test The process used to ensure that triggers and actions function properly when constructing a flow. ## See Also - [Mulesoft Composer: Overview](https://docs.mulesoft.com/composer/ms_composer_overview) - [MuleSoft Composer: Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) - [Composer Connector Reference](https://docs.mulesoft.com/composer/ms_composer_reference) - [Knowledge Articles](https://help.salesforce.com/s/) --- product: Composer --- # MuleSoft Composer Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Use MuleSoft Composer to build connected experiences faster. You don’t need to wait for development resources to unlock data, integrate apps, and automate business processes that create real customer value. New versions are automatically available once they are released; you don’t need to perform any tasks to move to the new version. See [Known Issues and Limitations for MuleSoft Composer](https://docs.mulesoft.com/composer/ms_composer_ms_release_notes_ki) for a list of known issues and limitations by date. ## October 22, 2026 ### Fixed Issues

Issue Resolution	ID
ServiceNow Connector now returns an `INVALID_WSDL` error instead of parsing WSDL documents that contain any of the following: A DOCTYPE declaration An XInclude element An absolute import, include, or redefine reference in a WSDL or XML schema Relative WSDL and schema imports continue to work.	W-24541378

## May 28, 2026 ### Fixed Issues

Issue Resolution	ID
To prevent excessive errors from abandoned processes and reduce the risk of service incidents, MuleSoft Composer automatically deactivates flows that experience continuous failures and alerts affected users. Deactivation occurs only when a flow meets both of these conditions: 100 or more consecutive errors 10 or more days of continuous failure You can reactivate a deactivated flow at any time.	W-22571502

## March 19, 2026 ### Fixed Issues

Issue Resolution	ID
Jira Connector now correctly updates the watermark for the triggers, and captures all subsequent new and updated issues.	W-20186115
In Jira Connector, all triggers now correctly update the watermark when multiple records share the same minute-level timestamp. The connector now uses cursor-based pagination to retrieve all records for a specific watermark before updating the watermark value. This prevents duplicate record retrieval and resolves issues where flows enter an indefinite waiting state.	W-21090825

## November 17, 2025 ### Fixed Issues

Issue Resolution ID

Issue Resolution	ID
In Xero Connector, the On New or Updated Invoice trigger now accepts the following values in the Invoice Type field: `ACCPAYCREDIT` (Accounts Payable Credit Note) `ACCRECCREDIT` (Accounts Receivable Credit Note) `APOVERPAYMENT` (Accounts Payable Overpayment) `APPREPAYMENT` (Accounts Payable Prepayment) `AROVERPAYMENT` (Accounts Receivable Overpayment) `ARPREPAYMENT` (Accounts Receivable Prepayment)	W-19889137

In Xero Connector, the On New or Updated Invoice trigger now accepts the following values in the Invoice Type field:

ACCPAYCREDIT (Accounts Payable Credit Note)
ACCRECCREDIT (Accounts Receivable Credit Note)
APOVERPAYMENT (Accounts Payable Overpayment)
APPREPAYMENT (Accounts Payable Prepayment)
AROVERPAYMENT (Accounts Receivable Overpayment)
ARPREPAYMENT (Accounts Receivable Prepayment)

W-19889137

## October 29, 2025 ### Fixed Issues

Issue Resolution	ID
In QuickBooks Connector, the Create Estimate action no longer fails when the Expiration Date and Due Date field values are provided in the flow.	W-18116231

## October 7, 2025 ### Fixed Issues

Issue Resolution	ID
Jira Connector now correctly processes search results for triggers by removing the total field from parsing.	W-19586865

## September 18, 2025 ### Fixed Issues

Issue Resolution	ID
In Jira Connector, the `/rest/api/3/search/jql` endpoint is used instead of the `/rest/api/3/search` endpoint.	W-19470768

## July 9, 2024 ### Fixed Issues

Issue Resolution	ID
In Workday Connector, testing a flow that has an error handler containing a Workday connection no longer gets stuck in the processing status and incorrectly fails with the `Test failed because of external errors. Please try again.` error.	W-15239656

## May 17, 2024 ### Fixed Issues

Issue Resolution	ID
NetSuite Connector no longer fails to retrieve custom values in an Inventory record.	W-15138793
In NetSuite Connector, the Get Records action now returns the correct `Internal ID` for values in fields containing multiple picklists.	W-15194262

## March 21, 2024 ### What’s New - You can now view descriptions of connector actions and triggers directly under their respective names. ## March 15, 2024 ### Fixed Issues

Issue Resolution	ID
After an access token expires, Salesforce Marketing Cloud Connector now properly refreshes the access token.	W-14979479

## March 11, 2024 ### Fixed Issues

Issue Resolution	ID
In Jira Connector, you can now create new connections in Composer as intended.	W-15070963

## February 28, 2024 ### Fixed Issues

Issue Resolution	ID
Microsoft Dynamics 365 Business Central Connector no longer incorrectly fails with an `Invalid Connection` error when creating a connection.	W-14824218

## February 26, 2024 ### What’s New - A beta feature is now available to enhance automation and integration which allows you to publish your activated Composer Flows to a trusted Salesforce organization. ## January 9, 2024 ### What’s New - For triggers in the following connectors, the **Polling Frequency** field is now required: - Microsoft Dynamics 365 Business Central - Workday - Xero This field enables you to select how often Composer makes a request to the underling system API to look for changes to records in active flows. ## December 14, 2023 ### What’s New - For triggers in the following connectors, the **Polling Frequency** field is now required: - MuleSoft RPA - Sage Intacct - SAP S/4HANA Cloud - ServiceNow - Slack - Snowflake - Zendesk This field enables you to select how often Composer makes a request to the underling system API to look for changes to records in active flows. - API Sharing is now available for single-tenant, Anypoint Platform organizations in Composer. API Sharing is limited to the Exchange API Asset in the same Anypoint organization. This enables Composer to expand the connectivity to more systems, to have more control over both API management and governance, and to consume complex APIs built in Anypoint Platform. ## December 6, 2023 ### What’s New - For triggers in the following connectors, the **Polling Frequency** field is now required: - Asana - Box - Gmail - Google Big Query - Google Sheets - Hubspot - Jira - Marketo - Netsuite This field enables you to select how often Composer makes a request to the underling system API to look for changes to records in active flows. ## December 1, 2023 ### What’s New - For triggers in QuickBooks Online Connector and Stripe Connector, the **Polling Frequency** field is now required. This field enables you to select how often Composer makes a request to the underling system API to look for changes to records in active flows. ## November 20, 2023 ### What’s New - A new page, **Connections**, is available in the navigation pane. Using this page, you can easily view connections, see which flows currently use each connection, delete connections, and edit the names of connections. ## November 15, 2023 ### What’s New - Salesforce Connector now supports Salesforce API v59.0. ## November 14, 2023 ### What’s New - For triggers in Salesforce Connector, the **Polling Frequency** field is now required. This field enables you to select how often Composer makes a request to the underling system API to look for changes to records in active flows. ## November 13, 2023 ### What’s New - You can now search for templates (by template name, connector name, or template description) and filter templates (by use case category or connector). ## October 31, 2023 ### What’s New - When selecting outputs for an Invocable Flow, the `List` and `List

Issue Resolution	ID
QuickBooks Connector now includes an enhanced implementation for input parameters, such as better mapping when input parameters are not specified or are `null`.	W-13280661
In NetSuite Connector, custom fields now appear as intended.	W-13222742, W-13304252, W-13481333

Issue Resolution	ID
Snowflake Connector now validates account names by checking for invalid special characters.	W-12598991
In NetSuite Connector, the Get Records action now correctly supports the OTHER_CHARGE_SALE_ITEM record type.	W-13001785

Issue Resolution	ID
Error messages in HTTP Connector now display more precise error types.	W-12483461
When you complete the Operation Values field in REST Consumer Connector, an error indicating that a value is required no longer occurs.	W-12648223
Rest Consumer Connector now properly recognizes the values provided in the Client Secret and Client ID fields while using API Sharing.	W-12601570

Issue Resolution	ID
In NetSuite Connector, the Get Records action no longer returns the incorrect record for the LOT_NUMBERED_ASSEMBLY_ITEM record type.	W-12473442
In NetSuite Connector, the USER_ERROR: Invalid log in attempt error no longer occurs.	W-12619973
In NetSuite Connector, the Name field no longer appears in write operations.	W-12428757
In NetSuite Connector, the Type dropdown in the Get Records action no longer causes a NETSUITE_SOAP_FAULT error.	W-12572300
The NetSuite Connector no longer fails to parse the com.sun.xml.internal.stream.events.EndElementEvent error response.	W-12573323

Issue Resolution	ID
In Jira Connector, the metadata output for the `labels` property now returns an array of strings instead of an array of empty objects.	W-11899482
In Jira Connector, the Retrieve attachment action now shows the detailed error message returned by the Jira endpoint.	W-12282452

Issue Resolution	ID
In NetSuite Connector, metadata load logging is now enhanced.	W-12412287, W-12244102
In NetSuite Connector, records now show custom segments as intended.	W-12244102

Issue	ID
In NetSuite Connector, `NullFieldsList` is no longer included in the metadata.	W-12029245
In NetSuite Connector, External ID is now shown in custom fields when creating or updating a record.	W-11951099
In NetSuite Connector, errors are no longer overridden when warnings are present.	W-12165594

Issue Resolution	ID
In ServiceNow Connector, the New/Updated Record trigger now picks up messages for all appropriate timestamps.	W-12176039
In ServiceNow Connector, sudden disconnections in high workload scenarios no longer occur.	W-12035222
In ServiceNow Connector, the componentorg.apache.commons library is upgraded to version 1.10.0 to address reported security vulnerabilities.	W-11913979
In ServiceNow Connector, the org.springframework library is upgraded to version 5.3.20 to address reported security vulnerabilities.	W-12150392
In Salesforce Connector, the triggers and the Get records action now support the `isTrue` and `isFalse` operators for boolean parameters.	W-11752116
In Salesforce Connector, the Delete record action no longer incorrectly throws a `Retrieving metadata for the step failed. Try saving and refreshing the page.` error.	W-12211471
In Salesforce Connector, the triggers no longer have a potential data loss when the watermark is not used properly.	W-12128874
In Jira Connector, the com.fasterxml.jackson.core library is upgraded to version 2.14.1 to address reported security vulnerabilities.	W-11933499
In Jira Connector, the org.apache.commons-text library is upgraded to version 1.10.0 to address reported security vulnerabilities.	W-12004679

Issue Resolution	ID
In Zendesk Connector, the com.fasterxml.jackson.core library is upgraded to version 2.13.4.1 to address reported security vulnerabilities.	W-11933496
In Zendesk Connector, the connection no longer breaks when Zendesk triggers are idle for long durations when deployed on CloudHub.	W-12040415

Issue Resolution	ID
In NetSuite Connector, the Jackson Databind library is upgraded to version 2.13.4.2 to address reported security vulnerabilities.	W-11963381
When connected to Jira, HTTP Connector now retrieves error messages when errors occur. Previously errors were only recorded in the Jira log.	W-11816468
When connected to Shopify, HTTP Connector flow tests no longer run indefinitely and return errors.	W-11821763, W-11819981

Issue Resolution	ID
In Jira Connector, the Result filter has been removed and now tests no longer fail when fields are selected.	W-11510054
In Jira Connector, the number of Jira projects that appeared in a dropdown was limited. Now, all Jira projects are retrieved in the dropdown.	W-11912169

Issue Resolution	ID
Fixed the issue in Google Sheets Connector in which an `InterruptedException` occurred during an MUnit test.	W-10887516
Fixed the issue in Google Sheets Connector in which the Create row action did not work properly when the first column without a header contained values.	W-10933097
In Google Sheets Connector, the com.fasterxml.jackson.core library is upgraded to version 2.13.4.	W-11719209

Issue Resolution	ID
Fixed the issue in HTTP Connector in which the test connectivity was not triggering a refresh with an OCS connection.	W-11469764
Fixed the issue in HTTP Connector in which OAuth 2.0 refresh tokens from Shopify were not valid.	W-11437322
Fixed the issue in HTTP Connector in which fields containing an escape sequence (for example, `\r` for a carriage return) were not properly parsed.	W-11072611
Fixed the issue in Quickbooks Connector where Sample Data output returned more than one record, even in the case of arrays that are nested fields.	W-11388800

Issue Resolution	ID
In Workday Connector, the connection validation now succeeds even if the user does not have access to the `Performance_Management` service.	W-11193505
Fixed reported security vulnerabilities in Workday Connector by upgrading the Spring Framework library from `org.springframework:spring-context:5.3.18` to `org.springframework:spring-context:5.3.20`.	W-11195299

Issue Resolution	ID
ServiceNow Connector now loads metadata for all WebService accessible tables automatically.	W-10919969
In ServiceNow Connector, patched security vulnerability in dependency `org.springframework : spring-beans : 5.3.17`.	W-10981860
In ServiceNow Connector, patched security vulnerability in dependency `org.springframework : spring-context : 5.2.7.RELEASE`.	W-11001899

Issue Resolution	ID
Fixed the issue in Workday Connector in which you could not filter fields containing values with the file data type.	W-10574439 COCN-667
In Workday Connector, when editing a Job Requisition action, the Position Time Type field is now selectable as a list or set as a data pill.	W-10574489 COCN-605
When a generic error message is returned from the API in Workday Connector, the error message that occurs in Composer is now informative.	W-10574413 COCN-705
Improved validation error messages in Workday Connector to make them more specific.	W-10574467 COCN-632
In Workday Connector, the Position Title, Supervisory Organization, and Location fields are now optional in the Create Worker action. However, if the Location value is not set on the Position object, then the Location field is required, or the Create Worker API operation will fail.”	W-10574483 COCN-612
In Jira Connector, pagination is now enabled to fetch all assignable users in the Reporter and Assignee fields when using the Create issue with custom fields action.	W-10934109

Issue	ID
Updated error messages in Google Sheets Connector for empty list fields in the Create Row action.	W-10574328
Fixed the issue in Google Sheets Connector in which columns without headers were incorrectly assigned the header of the next column with a header.	W-10899109

Issue	ID
Previously, in Google Sheets Connector when Google Sheets was the trigger, all output fields were returned as `text` regardless of the assigned data type (for example, `int` or `bool`). As a result, if you attempted to map the trigger data pills to non-text fields in the action, you encountered an error. Now, trigger fields retain their original data types and you can map them appropriately in subsequent actions.	SE-227701, COCN-575
Fixed an issue in Google Sheets Connector in which metadata from a document containing a space failed.	COCN-742
Upgraded library dependencies.

Issue	ID
Fixed metadata pagination issues in Xero Connector.	CSCA-1106
Fixed failing sample data requests for the Get contact by ID and Search contacts actions in Xero Connector.	CSCA-1044
Fixed the field labels in Xero Connector to match the corresponding field names in the Xero APIs.	CSCA-1043
Fixed field labels in Xero Connector.	CSCA-1040

Issue	ID
When some metadata subcategories are empty, metadata can be refreshed in the flow.	SE-23496
Fixed the issue when processing custom fields with empty values.	SE-23068
The NetSuite XML request no longer requires the runServerSuiteScriptAndTriggerWorkflows flag.	SE-22758
Fixed the issue when processing date/time custom fields.	COCN-735

Record Type	Trigger	Action
BILLING_SCHEDULE		X
CASH_SALE	X	X
CASH_REFUND	X	X
CLASSIFICATION		X
CONTACT	X	X
CREDIT_MEMO	X	X
CURRENCY		X
CURRENCY_RATE		X
CUSTOMER	X	X
CUSTOMER_DEPOSIT	X	X
CUSTOMER_PAYMENT	X	X
CUSTOMER_REFUND	X	X
CUSTOM_RECORD_TYPES	X	X
DEPARTMENT		X
ESTIMATE	X	X
EMPLOYEE	X	X
GIFT_CERTIFICATE_ITEM	X	X
INVENTORY_ADJUSTMENT	X	X
INVENTORY_ITEM	X	X
INVOICE	X	X
ITEM_FULFILLMENT	X	X
ITEM_GROUP	X	X
ITEM_RECEIPT	X	X
JOURNAL_ENTRY	X	X
KIT_ITEM	X	X
LEAD	X	X
LOCATION		X
LOT_NUMBERED_ASSEMBLY_ITEM	X	X
LOT_NUMBERED_INVENTORY_ITEM	X	X
NON_INVENTORY_PURCHASE_ITEM	X	X
NON_INVENTORY_RESALE_ITEM	X	X
NON_INVENTORY_SALE_ITEM	X	X
OPPORTUNITY	X	X
OTHER_CHARGE_PURCHASE_ITEM	X	X
OTHER_CHARGE_RESALE_ITEM	X	X
OTHER_CHARGE_SALE_ITEM	X	X
PARTNER	X	X
PAYMENT_ITEM	X	X
PRICE_LEVEL		X
PROSPECT	X	X
PURCHASE_ORDER	X	X
RETURN_AUTHORIZATION	X	X
SALES_ORDER	X	X
SERIALIZED_ASSEMBLY_ITEM	X	X
SERIALIZED_INVENTORY_ITEM	X	X
SERVICE_PURCHASE_ITEM	X	X
SERVICE_RESALE_ITEM	X	X
SERVICE_SALE_ITEM	X	X
SUBSIDIARY		X
SUPPORT_CASE	X	X
TIME_BILL	X	X
TIME_SHEET	X	X
TRANSFER_ORDER	X	X
VENDOR	X	X
VENDOR_BILL	X	X

Data Type	Definition
Boolean	Evaluates to `true` or `false`.
Date	Stores a year, month, and day as `yyyy-MM-dd`.
DateTime	Stores a date and time within a time zone relative to Coordinated Universal Time (UTC). Composer does not store the user’s local timezone; therefore, when a `DateTime` value is entered in this field, Composer assumes that the `DateTime` value entered is in UTC format. A time zone must include either the symbol `+` in the time value or the symbol `-` in the date value. For example, 12:30 p.m. on June 1, 2019, in the Macau time zone is represented as `2019-06-01T12:30:00+08:00`. Note that when using the `today()` function, the value for `Date` is returned in UTC. Additionally, if the date is not entered in UTC, Composer will automatically convert the date to UTC format which may or may not be accurate for the user’s local time zone which could affect the resulting logic.
List<Object>	Returns a list of objects, for example, the output of the Get Records action.
List<Primitive>	Returns a list containing primitive data types. The following item data types are available: `Boolean`, `Date`, `DateTime`, `Integer`, `Number`, and `String`.
Number	Stores either a floating-point number in the range of 1.40129846432481707e-45 to 3.40282346638528860e+38 or an integer.
Object	Refers to a composite data type that can contain other data types as properties (`boolean`, `date`, `number`, and so on).
String	Stores text, numbers that are not `number` data types, or a combination of both, for example, 94u0sfjlk*(f!`lkkjd, `18005555555`, or `Fred`.

Function Name	Description	Example	Parameter Definition	Input Data Type Parameters	Output Data Type
lower	Returns the provided string in lowercase characters.	`lower(COMPOSER) = composer`	NA	text: String	String
upper	Returns the provided string in uppercase characters.	`upper(composer) = COMPOSER`	NA	text: String	String
capitalize	Capitalizes the first letter of each word in a string. This also removes underscores between words and puts a space before each capitalized word.	`capitalize(name) = Name` `capitalize(firstName) = First Name` `capitalize(customer_first_name) = Customer First Name`	NA	text: String	String
trim	Removes any blank spaces from the beginning and end of a string.	`trim(<long example text>) = this example long text`	NA	text: String	String
first	Returns the specified number of characters from the beginning of a string. If the number is equal to or greater than the number of characters in the string, the function returns the entire string.	`first(Hello Composer!, 5) = Hello`	NA	text: String numCharacters: Number	String
last	Returns the specified number of characters from the end of a string.	`last(Hello Composer!, 9) = Composer!`	NA	text: String numCharacters: Number	String
substitute	Replaces all substrings that match a literal search string with a specified replacement string. Replacement proceeds from the beginning of the string to the end. For example, the result of replacing `aa` with `b` in the string `aaa` is `ba`, rather than `ab`.	`substitute(Composer, o, O) = COmpOser` `substitute(Composer, a, Example) = Composer`	NA	text: String target: String replacement: String	String
fromStringToBoolean	Transforms a string input value into a boolean value.	`fromStringToBoolean(true) = true` `fromStringToBoolean(FALSE) = false` `fromStringToBoolean(TrUe) = true`	NA	text: String	Boolean
fromStringToDate	Transforms a string input value into a date value. Accepts a format and locale. The format parameter represents the format of the input string. The default format is `uuuu-MM-dd` and the default locale is en-US; however, these defaults can be modified.	`fromStringToDate(2021-03-15, uuuu-MM-dd, en-US) = 2021-03-15` `fromStringToDate(2021/15/03, uuuu/dd/MM, en-US) = 2021-03-15`	Format: The format parameter represents the format of the input string. This parameter accepts Java character patterns based on ISO-8601. A Date value, such as `2011-12-03`, has the format `uuuu-MM-dd`. Locale: Optional ISO 3166 country code to use, such as `en-US`, `AR`, or `ES`.	text: String format: String locale: String	Date
fromStringToDateTime	Transforms a string input value into a dateTime value. Accepts a format and locale. The format parameter represents the format of the input string. The default format is `uuuu-MM-dd’T’HH:mm:ssz` and the default locale is en-US; however, these defaults can be modified.	`fromStringToDateTime(2021-03-15T23:57:59Z,uuuu-MM-dd’T’HH:mm:ssz,US) = 2021-03-15T23:57:59Z` `fromStringToDateTime(2021-03-15 23:57:59Z,uuuu-MM-dd HH:mm:ssz,en-US) = 2021-03-15T23:57:59Z`	Format: The format parameter represents the format of the input string. This parameter accepts Java character patterns based on ISO-8601. A DateTime value, such as `2011-12-03T10:15:30.000000+01:00`, has the format `uuuu-MM-dd HH:mm:ssz`. Locale: Optional ISO 3166 country code to use, such as `en-US`, `AR`, or `ES`.	text: String format: String locale: String	DateTime
fromStringToNumber	Transforms a string input value into a number value.	`fromStringToNumber(1) = 1` `fromStringToNumber(0.05) = 0.05`	NA	text: String	Number
emptyString	Returns an empty string. You can use the emptyString function wherever an empty string is needed, including as an input parameter in other functions.	`-`	`-`	String
substring	Returns a substring that spans from the character at the specified `from` index to the last character before the `until` index.	`substring(Hello Composer, 6, 14) = Composer`	N/A	text: String from: Number until: Number	String

Function Name	Description	Example	Parameter Definition	Input Data Type Parameters	Output Data Type
round	Rounds a number up or down to the nearest whole number.	`round(1.2) = 1` `round(4.6) = 5` `round(3.5) = 4`	NA	number: Number	Number
ceil	Rounds a number up to the nearest whole number.	`ceil(1.2) = 2` `ceil(3) = 3`	NA	number: Number	Number
floor	Rounds a number down to the nearest whole number.	`floor(2.2) = 2` `floor(3) = 3`	NA	number: Number	Number
abs	Returns the absolute value of a number.	`abs(-3.4) = 3.4` `abs(2) = 2`	NA	number: Number	Number
fromNumberToString	Transforms a number value (whole or decimal) into a string value.	`fromNumberToString(1) = 1` `fromNumberToString(0.05) = 0.05`	NA	number: Number	String
fromNumberToDateTime	Transforms a number input value into a dateTime value. Uses milliseconds or seconds as the unit. The default unit is seconds.	`fromDateTimeToNumber(1443743879, seconds) = 2015-10-01T23:57:59Z` `fromDateTimeToNumber(1443743879000, milliseconds) = 2015-10-01T23:57:59Z`	Unit: The unit of time to use for the conversion: "milliseconds" or "seconds". The default unit is "seconds."	unit: String	DateTime

Function Name	Description	Example	Parameter Definition	Input Data Type Parameters	Output Data Type
today	Returns the date for today as a Date type.	`today() = 2021-03-15`	NA	NA	Date
now	Returns a DateTime value for the current date and time.	`now() = 2021-03-15T18:23:20`	NA	NA	DateTime
addDays	Creates and returns a Date value incremented or decremented by the specified number of days.	`addDays(today(), 3) = 2021-03-18` `addDays(2021-03-15, -4) = 2021-03-11`	NA	date: Date numDays: number	Date
addDays	Creates and returns a DateTime value incremented or decremented by the specified number of days.	`addDays(now(), 3) = 2021-03-18T18:23:20` `addDays(2021-03-15T18:23:20, 3) = 2021-03-18T18:23:20`	NA	dateTime: DateTime numDays: number	DateTime
addMonths	Creates and returns a Date value incremented or decremented by the specified number of months.	`addMonths(today(), 3) = 2021-06-15` `addMonths(2021-03-15, -4) = 2020-12-15`	NA	date: Date numMonths: number	Date
addMonths	Creates and returns a DateTime value incremented or decremented by the specified number of months.	`addMonths(now(), 3) = 2021-06-15T18:23:20` `addMonths(2021-03-15T18:23:20, -4) = 2020-12-15T18:23:20`	NA	dateTime: DateTime numMonths: number	DateTime
addYears	Creates and returns a Date value incremented or decremented by the specified number of years.	`addYears(today(), 1) = 2022-03-15` `addYears(2021-03-15, -1) = 2020-03-15`	NA	date: Date numYears: number	Date
addYears	Creates and returns a DateTime value incremented or decremented by the specified number of years.	`addYears(now(), 3) = 2024-03-15T18:23:20` `addYears(2021-03-15T18:23:20, -1) = 2020-03-15T18:23:20`	NA	dateTime: DateTime numYears: number	DateTime
addHours	Creates and returns a DateTime value incremented or decremented by the specified number of hours.	`addHours(now(), 1) = 2021-03-15T23:23:20` `addHours(2021-03-15T22:23:20, 3) = 2021-03-16T01:23:20` `addHours(2021-03-15T22:23:20, -4) = 2021-03-15T18:23:20`	NA	dateTime: DateTime numHours: number	DateTime
addMinutes	Creates and returns a DateTime value incremented or decremented by the specified number of minutes.	`addMinutes(now(), 5) = 2021-03-15T18:33:20` `addMinutes(2021-03-15T23:45:00,15) = 2021-03-16T00:00:00` `addMinutes(2021-03-15T18:23:20, -30) = 2021-03-15T17:53:20`	NA	dateTime: DateTime numMinutes: number	DateTime
addSeconds	Creates and returns a DateTime value incremented or decremented by the specified number of seconds.	`addSeconds(now(), 30) = 2021-03-15T18:23:50` `addSeconds(2021-03-15T23:45:00,15) = 2021-03-15T23:45:30` `addSeconds(2021-03-15T18:23:20, -30) = 2021-03-15T18:22:50`	NA	dateTime: DateTime numSeconds: number	DateTime
beginningOfHour	Returns a new DateTime value that changes the Time value in the input to the beginning of the specified hour. The minutes and seconds in the input change to 00:00.	`beginningOfHour(2021-03-15T18:23:20) = 2021-03-15T18:00:00`	NA	dateTime: DateTime	DateTime
beginningOfDay	Returns a new DateTime value that changes the Time value in the input to the beginning of the specified day. The hours, minutes, and seconds in the input change to 00:00:00.	`beginningOfDay(2021-03-15T18:23:20) = 2021-03-15T00:00:00`	NA	dateTime: DateTime	DateTime
beginningOfWeek	Returns a new Date value that changes the Day value from the input to the beginning of the first day of the specified week. The function treats Sunday as the first day of the week.	`beginningOfWeek(2021-03-15) = 2021-03-14` `beginningOfWeek(today()) = 2021-03-14`	NA	date: Date	Date
beginningOfWeek	Returns a new DateTime value that changes the Day and Time values from the input to the beginning of the first day of the specified week. The function treats Sunday as the first day of the week.	`beginningOfWeek(2021-03-15T18:23:20) = 2021-03-14T00:00:00` `beginningOfWeek(now()) = 2021-03-14T00:00:00`	NA	dateTime: DateTime	DateTime
beginningOfMonth	Returns a new Date value that changes the Day value from the input to the first day of the specified month.	`beginningOfMonth(2021-11-15) = 2021-11-01` `beginningOfMonth(today()) = 2021-03-01`	NA	date: Date	Date
beginningOfMonth	Returns a new DateTime value that changes the Day value from the input to the first day of the specified month. The day and time in the input changes to `01T00:00:00`.	`beginningOfMonth(2021-03-15T18:23:20) = 2021-03-01T00:00:00` `beginningOfMonth(now()) = 2021-03-01T00:00:00`	NA	dateTime: DateTime	DateTime
beginningOfYear	Returns a new Date value that changes the Month and Day values from the input to the first day of the specified year.	`beginningOfYear(2021-11-15) = 2021-01-01` `beginningOfYear(today()) = 2021-01-01`	NA	date: Date	Date
beginningOfYear	Returns a new DateTime value that changes the Month and Day values from the input to the first day of the specified year. It also sets the Time value to `00:00:00`. The month, day, and time in the input changes to `01-01T00:00:00`.	`beginningOfYear(2021-03-15T18:23:20) = 2021-01-01T00:00:00` `beginningOfYear(now()) = 2021-01-01T00:00:00`	NA	dateTime: DateTime	DateTime
daysBetween	Returns the number of days between two dates. If the to Date value is earlier than the from Date value, the function returns a negative number equal to the number of days between the two dates.	`daysBetween(2020-03-15, 2021-03-15) = 365`	NA	from: Date to: Date	Number
daysBetween	Returns the number of days between two DateTime values. If the to DateTime value is earlier than the from DateTime value, the function returns a negative number equal to the number of days between the two DateTime values.	`daysBetween(2020-03-15T18:23:20, 2021-03-15T02:23:20) = 365`	NA	from: DateTime to: DateTime	Number
month	Returns the numerical value of the month in the Date input.	`month(2021-03-15) = 3`	NA	date: Date	Number
month	Returns the numerical value of the month in the DateTime input.	`month(2021-03-15T18:23:20) = 3`	NA	dateTime: DateTime	Number
year	Returns the numerical value of the year in the Date input.	`year(2021-03-15) = 2021`	NA	date: Date	Number
year	Returns the numerical value of the year in the DateTime input.	`year(2021-03-15T18:23:20) = 2021`	NA	dateTime: DateTime	Number
fromDateToString	Transforms a date input value into a string value. Accepts a format and locale. The format parameter represents the required format of the output string. The default format is `uuuu-MM-dd` and the default locale is en-US; however, these defaults can be modified.	`fromDateToString(2021-03-15, uuuu-dd-MM, en-US) = 2021-15-03` `fromDateToString(2021-03-15, uuuu/MM/dd, en-US) = 2021/03/15` `fromDateToString(2021-03-15, eeee, dd MMMM, ES) = lunes, 15 marzo`	Format: The ISO-8601 formatting to use on the Date. It represents the desired format of the output string. For example, this parameter accepts character patterns based on the Java 8 java.time.format. The default format is `uuuu-MM-dd`. Locale: Optional ISO 3166 country code to use, such as `en-US`, `AR`, or `ES`. When you pass a translatable format, such as `eeee` and `MMMM`, a locale (such as `ES`) transforms the corresponding numeric values to a localized string.	date: Date format: String locale: String	String
fromDateTimeToString	Transforms a dateTime input value into a string value. Accepts a format and locale. The format parameter represents the desired format of the output string. The default format is `uuuu-MM-dd’T’HH:mm:ssz` and the default locale is en-US; however, these defaults can be modified.	`fromDateTimeToString(2021-03-15T23:57:59Z, uuuu-MM-dd’T’HH:mm:ssz, en-US) = 2021-03-15T23:57:59Z` `fromDateTimeToString(2021-03-15T23:57:59Z, MMMM dd, ES) = marzo 15`	Format: The ISO-8601 formatting to use on the DateTime. It represents the desired format of the output string. For example, this parameter accepts character patterns based on the Java 8 java.time.format. The default format is `uuuu-MM-dd’T’HH:mm:ssz`. Locale: Optional ISO 3166 country code to use, such as `en-US`, `AR`, or `ES`. When you pass a translatable format, such as `eeee` and `MMMM`, a locale (such as `ES`) transforms the corresponding numeric values to a localized string.	dateTime: DateTime format: String locale: String	String
fromDateTimeToNumber	Transforms a dateTime input value into a number value. The number is in milliseconds or seconds, depending on the selected unit. The default unit is seconds.	`fromDateTimeToNumber(2015-10-01T23:57:59Z, seconds) = 1443743879` `fromDateTimeToNumber(2015-10-01T23:57:59Z, milliseconds) = 1443743879000`	Unit: The unit of time to use for the conversion: "milliseconds" or "seconds". The default unit is "seconds."	dateTime: DateTime unit: String	Number
fromDateToDateTime	Transforms a date input value into a dateTime. It does so by adding a time. The default time is T00:00:00Z. All manual entries will be interpreted in UTC.	`fromDateToDateTime(2021-03-15, T00:00:00Z) = 2021-03-15T00:00:00Z` `fromDateToDateTime(2021-03-15, T23:57:59Z) = 2021-03-15T23:57:59Z`	NA	date: Date time: String	DateTime

Status (Salesforce)	Status (Zendesk)
New	New
Working	Open
Waiting on Customer	On-Hold
Escalated	Open
Closed	Closed

Function	Supported Data Type	Value Required?	Notes
Equals/Does not equal	All	Yes	The value in this field is case-sensitive for strings.
Contains/Does not contain	Array, String	Yes	None
Greater than/Less than	Date, Number	Yes	In the Date field, the Greater than value is equal to a later date and the Less than value is equal to an earlier date.
Greater than or equal/Less than or equal	Date, Number	Yes	In the Date field, the Greater than or equal value is equal to a later date or the current date and the Less than or equal value is equal to an earlier date or the current date.
Is empty/Is not empty	Array, String, Object	No	None
Starts with/Ends with	String	Yes	A string value for this field is required.
Is true/Is false	Boolean	No	None
Is present/Is not present	All	No	If the value in this field is null or if there is no value selected, then the value in this field is set to Not present by default.

Security Policy	Domain/Functional Areas	Permitted Security Groups
Set Up: Skills and Experience	Worker Profile and Skills	HR Administrator HR System Implementers Job and Position Administrator Learning Management System
	Implementation	Implementers
Special OX Web Services	Implementation