New Zoho CRM Triggers

We've added the following Triggers to our Zoho CRM connector

• New Lead
• New Contact
• New Account

Local Development

You probably write code for your web app on your computer. While developing, you're likely serving it via localhost and testing it in your browser. Need to add another feature? You write code, save, and refresh the browser. This iteration cycle tends to be fast.

With this new update, you can run your Rollout project similarly. Go to the root of your Rollout repo, start the local dev server, and point your UI components to use localhost:3300. Need to add a new trigger? Write code, save, and refresh the browser. It's both simpler and faster to use.

How it improves your development experience:

1. Faster iteration cycles since you don't have to deploy your project to the cloud to test
2. It is simpler to develop since it mirrors typical developer workflows
3. Multiple people on your team can develop integrations independently since everyone has a local testing environment
   

How do you set it up?

Follow this doc on how to run your project on your local machine: https://docs.rollout.com/documentation/local-development

Dark Mode

We've also shipped Dark Mode for your Rollout Dashboard. You can toggle your color scheme in the top right-hand corner of your dashboard.

New Connectors

In the last several weeks we've shipped the following connectors:

• Distru
• Dubber
• Google Drive
• Instagram
• Twilio Flex
  

Rollout V2

A new way to build your Rollout Connector

Instead of logging into the Rollout dashboard to define your app’s connector: triggers, actions, auth and queries, you can now do that from the comfort of your code editor. That’s right, we got rid of GUI, or as some have been calling it, the GU”ewwwww”I.

Time to dust off your neglected Vim editor or just return to your trusted Copilot and use the new Rollout framework to build out your connectors as a Rollout application that can live directly in your existing monorepo.

More info on how to migrate here: https://docs.rollout.com/guides/migrating-from-v1

Custom Connectors

While you’re building Connectors to your own application, you can also build out any custom or proprietary connectors to ANY applications with a living heartbeat working API. The framework enables you to use our battle tested libraries to define OAuth, connect to webhooks, or execute any custom logic in your triggers and actions. It opens up the possibility of tighter coupling with your applications business logic by being able to import and export libraries from your Rollout project.

Extending Pre-Built Connectors

You can now add new triggers or actions to one of Rollout’s existing connectors without having to worry about any details like Auth.

Dedicated Servers, Database and Queues

Each customer on V2 gets dedicated resources which have 2 benefits: your data and compute resources are separated from everyone else which is more secure. When some customers go viral and have large traffic spikes, it doesn’t affect your automations at all.

Your can host your Rollout resources wherever you want to meet various regulatory compliance standards.

Self-Hosting

Another benefit of moving to a single-tenant architecture is that Self-Hosting is now generally available. Contact us to learn more - yes, this is the verbiage that SaaS tools use for their enterprise tiers.

Git-Connected Deploys

You can finally deploy without having to use the Rollout dashboard. Connect your Rollout project to Github and deploy whenever you merge your code into a specific branch.

Production and Development Environments

Each customer will get multiple Rollout environments to separate development from production. Write code, merge it to your development branch and auto-deploy it to your development/staging environment for testing. Once that looks good, merge it to your main branch and auto-deploy to production. Finally a workflow that fits your software team.

Server Logs

See exactly what your dedicated server is doing, get raw API responses and error messages as your automations are being run.

We wrote a little more about why we decided to re-build our V2 here: https://rollout.com/blog/why-we-rebuilt-our-product-as-an-early-stage-startup

‍