Changelog

Use the most powerful application for team messaging to receive and send messages from Loop Message. No need to have any coding experience, just activate integration from the dashboard, and you’re all set.

You can use workflow automation by n8n to send/receive messages with the community node for Loop Message.

This integration may help ensure full responsibility for how long and where attachments from inbound messages are stored. You can share credentials from an AWS S3 Bucket or any other S3-compatible bucket, and all attachments from inbound messages will be stored in your bucket.

Starting December 1, 2025, we’ll be releasing the next generation of our API to the public. This is something we’ve been actively working on for the past year.

What does this mean for current customers?

For now, we plan to maintain the legacy API until the majority of our customers migrate to the new generation. We plan to do it in a few iterations during the winter.

• December 2025 - public beta
• December-January 2026 - stop accepting new sign-ups through the old backend. All new users will be able to sign up only through the new dashboard.
• February 2026 - moving all other users to the new backend with saving maximum backward compatibility.

We first began working on the iMessage API five years ago. Initially, when developing this API, we pursued specific goals that were relevant 5y ago. However, over the past few years, the market has undergone numerous changes, and we realized that a complete redesign of our backend would eventually be necessary.

Furthermore, a few products: iMessage API, Lookup, Auth, iOS, and macOS apps - operated under the LoopMessage brand that were unrelated to each other, which was confusing to some new customers.

Since January 2025, we’ll begin separating each product into its own brand. Each of these products now has its own separate backend and frontend with its own microservices. Previously, our API endpoints from all products operated as a single monolithic project, with a dozen microservices that also interacted with the API.

For the iMessage API, we’ll completely redesign the backend and frontend from scratch, as well as redesign many architectural issues that were not obvious five years ago. We also tried to incorporate into the new architecture the customer requests we had accumulated over the past few years.

You can use workflow automation by Pipedream to send/receive messages from Loop Message.

You can use workflow automation by Zapier to send/receive messages from Loop Message.

You can receive notifications with inbound iMessages to your email and reply through your email 📨

Therefore, you can now use iMessage on any platform that supports sending Emails 🤩

It could be Android, Desktop, CRM, SaaS, or even an old Nokia cellphone with any email client 📧

We have released demo chatbot with ChatGPT by OpenAI 🤖

This integration helps to quickly check how our iMessage API may works to build AI assistants 💬

The dashboard has been completely designed from scratch. Now it works much faster and more stable.