Ably adds native integrations for Zapier, IFTTT, and Cloudflare Workers

enhance-integ-zap-tftt-cflare-blog-01.0@2x(1).jpg

As of today Ably integrates with three new services, allowing you to act on realtime events in the Ably network by triggering actions and executing business logic across Zapier, IFTTT, and Cloudflare Workers. And, in the case of Zapier, publish to an Ably channel as part of a Zap workflow.

A common requirement in realtime messaging applications is for developers to be able to insert some business logic into a message processing pipeline. Typical use-cases might be to perform filtering or payload transformation on a message-by-message basis, either when first ingested into the messaging service, or as part of a rule that captures messages from one channel, applies the business logic, and then forwards the message to another channel.

Ably supports these use-cases through Reactor Integration rules that invoke cloud functions (e.g. AWS Lambdas or Google Cloud Functions). By providing a gateway to cloud functions from cloud services providers, we believe we provide the best available mechanism for these use-cases while making it easier to build with the ecosystems you’re already operating in.

Get started

How these new integrations work

All three integrations essentially use webhooks to communicate with these services. You can set up a Reactor Rule in your app dashboard to control exactly how and what you wish to communicate with your endpoint. This can vary from the data you want to send (message or presence events), which of your channels to send from, and which endpoint to send to. Once that’s done, Ably handles the logic, execution, and delivery.

IFTTT has known limitations

The IFTTT integration is fully functional but the capabilities are more limited than other integrations. This is down to how IFTTT accepts HTTP requests. Please read the IFTTT documentation for more info on this.

If you have any questions about these new integrations, or Reactor Integrations in general, please get in touch.

Ably .NET Client Library SDK release v1.1.18

Fixed bugs:

  • Cumulative retry timeout of 10s was exceeded
  • Connection moves to Failed when there is no internet connection
  • Could not load type of field IO.Ably.Transport.ConnectionManager

See GitHub for full release notes.

Ably Cocoa Client Library SDK release v1.1.20

Implemented changes:

  • Support build with Xcode 10 - brings in SocketRocket #5

Versions

Podfile

pod 'Ably', '1.1.20'

Cartfile

github "ably/ably-cocoa" == 1.1.20

Objective-C

#import <Ably/Ably.h>

Swift

import Ably

Compatibility

  • Carthage release for Swift is built with Xcode 11.2.

See GitHub for full release notes.

Ably Java Client Library SDK release v1.1.10

Implemented enhancements:

  • Remove capability to bundle messages

Closed issues:

  • Avoid message bundling, conforming to updated RTL6d

See GitHub for full release notes.

Ably Java Client Library SDK release v1.1.9

Implemented enhancements:

  • Maven deployment: add task for deploy to staging

Fixed bugs:

  • ConnectionManager.checkConnectivity() fails every time for Android 9
  • ably-java sometimes failing to decrypt Messages
  • Channels visibility improvements
  • ConnectionManager: use HTTPS for the internet-up check

See GitHub for full release notes.

Ably Java Client Library SDK release v1.1.8

Fixed bugs:

  • Rework and reinstate invalid ConnectionManager tests
  • After loss of connectivity, and transport closure due to timeout, the ConnectionManager still thinks the transport is active

See GitHub for full release notes.

Ably Cocoa Client Library SDK release v1.1.19

Fixed bugs:

  • Old push state AfterRegistrationUpdateFailed needs migration

Closed issues:

  • Auth token refresh misses when macOS is sleeping

Versions

Podfile

pod 'Ably', '1.1.19'

Cartfile

github "ably/ably-cocoa" == 1.1.19

Objective-C

#import <Ably/Ably.h>

Swift

import Ably

Compatibility

Carthage release for Swift is built with Xcode 11.2.

See GitHub for full release notes and a list of merged PRs.

Ably .NET Client Library SDK release v1.1.17

Fixed bugs:

  • Don't throw exceptions when there is a callback passed

See GitHub for full release notes.

Ably Cocoa Client Librardy SDK release v1.1.18

Fixed bugs:

  • Result of internet-up.ably-realtime.com is ignored
  • Realtime suspended connection retrial using wrong timeout

Closed issues:

  • Remove develop branch
  • Flaky test: RTP2f (incoming LEAVE while SYNCing)
  • Flaky test: RTN17* (fallback hosts) #931

Versions

Podfile

pod 'Ably', '1.1.18'

Cartfile

github "ably/ably-cocoa" == 1.1.18

Objective-C

#import <Ably/Ably.h>

Swift

import Ably

Compatibility

Carthage release for Swift is built with Xcode 11.2.

See GitHub for full release notes.

Ably .NET Client Library SDK release 1.1.16

Implemented enhancements:

  • Expose a custom way to notify the library about OperatingSystemNetworkState

Merged pull requests:

  • Allow to disable networkstate monitoring

See GitHub for full release notes.