Close menu
Explore Plans
Mobile menu Close menu

Chicago Transit Authority to Hubitat integrations

Automate your workflows between Chicago Transit Authority and Hubitat with IFTTT.

Create your own Chicago Transit Authority and Hubitat workflow

Create custom workflows effortlessly by selecting triggers, queries, and actions. With IFTTT, it's simple: “If this” trigger happens, “then that” action follows. Streamline tasks and save time with automated workflows that work for you.

44 triggers, queries, and actions

Device closes

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when your Hubitat device closes.

Device opens

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when your Hubitat device opens.

Device turns off

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when your Hubitat device turns off.

Device turns on

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when your Hubitat device turns on.

Mode changes

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when the Hubitat mode changes.

Motion is detected

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when new motion is detected.

Motion is no longer detected

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when motion is no longer detected.

New blue line alert

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when there is a new blue line rail alert from CTA.

New brown line alert

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when there is a new brown line rail alert from CTA.

New green line alert

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when there is a new green line rail alert from CTA.

New orange line alert

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when there is a new orange line rail alert from CTA.

New pink line alert

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when there is a new pink line rail alert from CTA.

History of blue line alerts

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when there is a new blue line rail alert from CTA.

History of brown line alerts

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when there is a new brown line rail alert from CTA.

History of Device turned off

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when your Hubitat device turned off.

History of green line alerts

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when there is a new green line rail alert from CTA.

History of Mode changes

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when the Hubitat mode has changed.

History of orange line alerts

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when there is a new orange line rail alert from CTA.

History of pink line alerts

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when there is a new pink line rail alert from CTA.

History of purple line alerts

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when there is a new purple line rail alert from CTA.

History of rail alerts

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when there is a new rail alert from CTA.

History of red line alerts

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when there is a new red line rail alert from CTA.

History of temperature rises above

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when the temperature rises above the specified threshold. Note: this query will only return future events after this Applet is created.

History of yellow line alerts

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when there is a new yellow line rail alert from CTA.

Change Mode

Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will change Hubitat's mode.

Close a device

Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will close a Hubitat device.

Dim a device

Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will change a device's dimmer level.

Lock a device

Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will lock a Hubitat device.

Open a device

Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will open a Hubitat device.

Turn off a device

Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will turn off your Hubitat switches, lights, sirens, strobes, etc.

Turn on a device

Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This Action will turn on a device attached to your Hubitat Elevation system.

Unlock a device

Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will unlock a Hubitat device.

Change Mode

Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will change Hubitat's mode.

Close a device

Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will close a Hubitat device.

Device closes

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when your Hubitat device closes.

Device opens

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when your Hubitat device opens.

Device turns off

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when your Hubitat device turns off.

Device turns on

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when your Hubitat device turns on.

Dim a device

Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will change a device's dimmer level.

History of blue line alerts

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when there is a new blue line rail alert from CTA.

History of brown line alerts

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when there is a new brown line rail alert from CTA.

History of Device turned off

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when your Hubitat device turned off.

History of green line alerts

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when there is a new green line rail alert from CTA.

History of Mode changes

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when the Hubitat mode has changed.

Build an automation in seconds!

You can add delays, queries, and more actions in the next step!

GET STARTED

How to connect to a Chicago Transit Authority automation

Find an automation using Chicago Transit Authority

Find an automation to connect to, or create your own!

Connect IFTTT to your Chicago Transit Authority account

Securely connect the Applet services to your respective accounts.

Finalize and customize your Applet

Review trigger and action settings, and click connect. Simple as that!
Get started

Upgrade your automations with

Start your free trial

More on Chicago Transit Authority and Hubitat

About Chicago Transit Authority

The Chicago Transit Authority (CTA) operates the nation’s second largest public transportation system. On an average weekday, 1.6 million rides are taken on CTA. This service lets you stay up to date on the latest service alerts across different service lines and optimize your commute.

Connect Chicago Transit Authority

More integrations with Chicago Transit Authority

About Hubitat

Hubitat Elevation is a powerful home automation platform that works with your connected devices. Hubitat is a local solution, not cloud-dependent, so it’s fast, reliable and private.

Connect Hubitat

More integrations with Hubitat