Mitto Connector

Using Descope's connectors allows you to use Mitto to send SMS with your own Mitto account. This article will guide you through setting up and using the Mitto connector.

Configure Mitto connector

Descope uses your Mitto account details such as API token, API secret, and sender information for integration.

To configure a Mitto connector, go to the Connectors page within the Descope Console, search for Mitto, and select the connector card.

Settings

Below is a list of applicable settings for the Mitto connector:

• Connector name: A custom name for your connector. This is useful if you're creating multiple connectors from the same template.
• Connector description: A brief description of the connector's purpose.
• API Token: Your Mitto API token required for authentication.
• API Secret: The secret key associated with your Mitto account.
• From: You can define the sender of the message in the following ways:
  • Phone Number: A number associated with your Mitto account, formatted with a country code.
  • Sender ID: If a custom sender ID is configured, this will be used to send the SMS.

You can test the connector configuration by clicking the Test button and viewing the Test Results panel.

Once complete, save your configuration by clicking Create.

Add your Mitto connector to a flow

Configure Mitto as the Default OTP Connector

To configure Mitto as your default connector for SMS-based OTP authentication, navigate to OTP within Authentication Methods and select the configured Mitto connector. You can further customize the OTP message template for Mitto; for more details, see our guide for Using Email and SMS Templates.

Once you have configured Mitto as the default connector for OTP authentication, Descope flows and any OTP calls via the API/SDK will utilize Mitto for OTP verification.

Using Mitto Explicitly in Flows

To override the default OTP connector in a flow to use Mitto, navigate to Flows and select your desired flow. Edit the action that initiates the OTP process (e.g., Sign In, Sign Up, or Sign Up or In with OTP via SMS). If the OTP action has not been added yet, you can add it by clicking the blue + icon at the top left, searching for the OTP action, and selecting it.

In this example, we update the Sign Up or In / OTP / SMS action to use the Mitto connector, overriding the configured default OTP method.

Once in edit mode for the OTP action, select the dropdown for the connector and choose the Mitto connector. After selecting Mitto, click done, and save your flow. You can also choose a customized template for more control; for details, see our guide for Using Email and SMS Templates. This action in your flow will now use the Mitto connector instead of the default OTP connector.

Sending Custom Messages via Mitto in Flows

There may be cases where you want to send a custom SMS that isn’t directly tied to the OTP authentication process. This section will explain how to use Mitto for custom messaging in your flows.

Navigate to: Flows, choose your flow, and tap the + icon to create a new action. Select Connector, and choose Mitto.

Click to set the connector in your flow editor and double-click the action to add the required fields:

• To: The recipient's phone number. You can set this dynamically based on previous flow attributes, such as {{user.phone}}.
• Message content: Enter the SMS content you want to send.

Now, place your connector at the appropriate point in the flow, such as after the user submits their phone number.

That's it! Whenever a user goes through your authentication flow, the Mitto connector will send an SMS automatically.