---
schema_version: "1"
id: 34ab729b1b3ab6c82e57545eefd9e2279018fa6e50d4882302b3758ed0f90bc1
title: Using Anypoint Studio to Configure Twilio Connector 4.2
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/twilio-connector/latest/twilio-connector-studio.md
canonical_url: https://docs.mulesoft.com/twilio-connector/latest/twilio-connector-studio
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 1a73f192f4c39aec9958d43c2942a6922374f6018ebbcb212238eb7feaaa9337
description: MuleSoft Documentation Site
release: "4.2"
latest: true
---
---
product: Twilio Connector
version: 4.2
is-latest-version: true
---

# Using Anypoint Studio to Configure Twilio Connector 4.2

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Studio (Studio) editors help you design and update your Mule applications, properties, and
configuration files.

To add and configure a connector in Studio:

1.  [Create a Mule project](#create-mule-project).

2.  [Add the connector to your Mule project](#add-connector-to-project).

3.  [Configure a source for the connector’s flow](#configure-input-source).

4.  [Add a connector operation to the flow](#add-connector-operation).

5.  [Configure a global element for the connector](#configure-global-element).

6.  [Configure the Other Connector Fields](#configure-other-fields).

When you run the connector, you can view the app log to check for problems in real time, as
described in [View the App Log](#view-app-log).

## Create a Mule Project

In Studio, create a new Mule project in which to add and configure the connector:

1.  In Studio, select **File > New > Mule Project**.

2.  Enter a name for your Mule project and click **Finish**.

## Add the Connector to Your Mule Project

Add Twilio Connector to your Mule project to automatically populate the XML code with the
connector’s namespace and schema location and to add the required dependencies to the project’s
`pom.xml` file:

1.  In the **Mule Palette** view, click **(X) Search in Exchange**.

2.  In the **Add Dependencies to Project** window, type `twilio` in the search field.

3.  Click **Twilio Connector** in **Available modules**.

4.  Click **Add**.

5.  Click **Finish**.

Adding a connector to a Mule project in Studio does not make that connector available to other
projects in your Studio workspace.

## Configure a Source

A source initiates a flow when a specified condition is met. You can configure one of these sources
to use with Twilio Connector:

- HTTP Listener  
  Initiates a flow each time it receives a request on the configured host and port

- Scheduler  
  Initiates a flow when a time-based condition is met

For example, to configure an HTTP Listener source, follow these steps:

1.  In the **Mule Palette** view, select **HTTP > Listener**.

2.  Drag **Listener** to the Studio canvas.

3.  On the **Listener** configuration screen, optionally change the value of the **Display Name**
    field.

4.  Specify a value for the **Path** field.

5.  Click the plus sign (**+**) next to the **Connector configuration** field to configure a global
    element that can be used by all instances of the HTTP Listener source in the app.

6.  On the **General** tab, specify the connection information for the connector.

7.  On the **TLS** tab, optionally specify the TLS information for the connector.

8.  On the **Advanced** tab, optionally specify reconnection information, including a reconnection
    strategy.

9.  Click **Test Connection** to confirm that Mule can connect with the specified server.

10. Click **OK**.

## Add a Connector Operation to the Flow

When you add a connector operation to your flow, you are specifying an action for that connector to
perform.

To add an operation for Twilio Connector, follow these steps:

1.  In the **Mule Palette** view, select **Twilio Connector** and then select the desired operation.

2.  Drag the operation onto the Studio canvas and to the right of the source.

## Configure a Global Element for the Connector

When you configure a connector, it’s best to configure a global element that all instances of that
connector in the app can use. Configuring a global element requires you to provide the
authentication credentials that the connector requires to access the target Twilio API. Twilio
Connector supports Basic authentication, which uses the Twilio Account SID as the username and Auth
Token as the password.

To configure the global element for Twilio Connector, follow these steps:

1.  Select the name of the connector in the Studio canvas.

2.  Select the operation in the Studio canvas.

3.  In the configuration screen for the operation, click the plus sign (**+**) next to the
    **Connector configuration** field to access the global element configuration fields.

    You can reference a configuration file that contains ANT-style property placeholders
    (recommended), or you can enter your authorization credentials in the global configuration
    properties. For information about the benefits of using property placeholders and how to
    configure them, see
    [Anypoint Connector Configuration](https://docs.mulesoft.com/connectors/introduction/intro-connector-configuration-overview).

4.  On the **Advanced** tab, optionally specify an expiration policy.

5.  Click **Test Connection** to confirm that Mule can connect with the specified server.

6.  Click **OK**.

## Configure Additional Connector Fields

Depending on the operation, configure the following fields on the operation’s properties window:

<table><colgroup><col> <col></colgroup><thead><tr><th>Field</th><th>Description</th></tr></thead><tbody><tr><td><p><strong>Account sid</strong></p></td><td><div><div><p>Unique ID of the account that sent this message</p></div></div></td></tr><tr><td><p><strong>Message sid</strong></p></td><td><div><div><p>Unique ID for the message</p></div></div></td></tr><tr><td><p><strong>Media sid</strong></p></td><td><div><div><p>Unique ID for the media</p></div></div></td></tr><tr><td><p><strong>Date Created</strong></p></td><td><div><div><p>Date on which the target media was created on Twilio, formatted as <code>YYYY-MM-DD</code></p></div></div></td></tr><tr><td><p><strong>Date Sent</strong></p></td><td><div><div><p>Date on which the target message was sent from Twilio, in RFC 2822 format</p></div></div></td></tr><tr><td><p><strong>From</strong></p></td><td><div><div><p>Phone number or sender ID that initiated the message, in E.164 format</p></div></div></td></tr><tr><td><p><strong>To</strong></p></td><td><div><div><p>Phone number that received a message, in E.164 format</p></div></div></td></tr></tbody></table>

For more information about each format, see the See Also section at the end of this document.

## View the App Log

To check for problems, you can view the app log as follows:

- If you’re running the app from Anypoint Platform, the output is visible in the Anypoint Studio
  console window.

- If you’re running the app using Mule from the command line, the app log is visible in your OS
  console.

Unless the log file path is customized in the app’s log file (`log4j2.xml`), you can also view the
app log in the default location `MULE_HOME/logs/<app-name>.log`.

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Using Anypoint Studio to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-studio)

- [Twilio Connector Reference](https://docs.mulesoft.com/twilio-connector/latest/twilio-connector-reference)

- [Salesforce Help](https://help.salesforce.com)