Explore Plans

Documentation

Connections

What are connections?

Connections allow you to power entire integrations between your service and another with one single connection. A user connects once using the connect button, and you can power multiple queries, triggers, and actions.

Connections vs Applets

Applets are 1:1. There's one trigger that happens on your service that maps to certain actions on another service. Also, Applets need to be configured on IFTTT and aren't compatible with queries.

Connections, on the other hand, are there to achieve multiple functions with a single integration. Connections allow you to set up queries, triggers, and actions for your users via the Connect API without the user having to enable anything on IFTTT. Just connect, authenticate, and you're ready to go.

Creating connections

Connection creation tool

The connection creation tool is designed for you to be able to build powerful integrations with any service on IFTTT. Connections created on the platform should be used in tandem with the Connect API, the iOS SDK, and the Android SDK.

How to use the tool

  1. Start by searching for and selecting the service you are looking to connect with
  2. Then add a feature and configure the triggers, queries, and actions you're going to use.
  3. Enter a title for the connection (e.g. "Control your Hue lights when you stream on Twitch") then click Update.
  4. A runtime script, if included, will run any time a new trigger event occurs for the connection.
  5. You'll now have access to Connect API endpoints for the selected queries, triggers, and actions.
  6. Leverage the Connect API along with the iOS SDK and Android SDK to programmatically execute queries, subscribe to triggers, and run actions for your users.

Tips on configuration

Connection query fields, trigger fields, and action fields can either be set by you as the developer or shown to the user to set themselves. How a connection is configured is dependent on the experience you're looking to create. See below for an example of how to use different configuration settings for different experiences.

Example: Control the color of your Hue lightbulbs

Service: Philips Hue Action: Change color

Use cases:

Change a user's Hue lights to blue An experience you're looking to create that only sets a user's Hue lights to blue.

Field name Visibility Value
Which lights? Customizable by the user Set by the user
Color value or name Set by you blue

Change a user's Hue lights to their favorite color An experience you're looking to create that sets a user's Hue lights to their favorite single color.

Field name Visibility Value
Which lights? Customizable by the user Set by the user
Color value or name Customizable by the user blue (default)

Change a user's Hue lights dynamically from your mobile app An experience you're powering where a user can change the color of their Hue lights directly from your mobile app.

Field name Visibility Value
Which lights? Customizable by the user Set by the user
Color value or name Set by you blue (default)

To change the color of the lights dynamically, be sure to include the following in the body of your action run request. This will overide the default value (blue).

{
  "fields": {
    "color": "purple",
  }
}

Testing and publishing your connections

  • To see the Connect API logs for a given connection, click the "API logs" tab and reference set of status codes.

  • Connections can be tested fully with the iOS and Android SDKs.

  • Publishing connections is only available for approved paid organizations. To learn more, contact sales.


Next steps: