Hey Everyone :wave: A new <Apollo.io> connector, ...
# announcements
e
Hey Everyone 👋 A new Apollo.io connector, a simple way to pause scheduled runs outside production, and a couple of fixes to make deployments and custom commands more reliable. ☁️ Prefer not to manage pipeline maintenance yourself? Meltano Cloud gives you fully managed connectors and direct access to our team. Here’s what’s new ✨ Features • New Apollo.io extractor: tap-apollo syncs your contacts, accounts, deals, tasks, calls, sequences and outreach emails, along with workspace reference data. Sequence rate fields that Apollo is still calculating load as null rather than failing the sync. • Pause scheduled runs per environment: we added support for disable_pipeline_schedules: true to an environment’s workspace file (e.g. workspace-staging.yml) to stop its scheduled runs and cut warehouse costs outside production. Manual runs and retries still work, and removing the line turns schedules back on. 🐛 Fixes • Custom commands in split project files: if your Meltano configuration is distributed across multiple files in the repository, custom commands you define in those files (like a custom dbt run) now work in Meltano Cloud pipelines. Previously these pipelines could fail with a “command could not be found” error. • GitHub webhook deployments: we noticed behaviour whereby GitHub webhooks were triggering multiple workspace deployments. It will now only happen once per merge into the target branch. 🚀A new connector, a way to pause scheduled runs where you don’t need them, and more reliable syncs. Thanks for the reports, and keep them coming! 📚 Curious which setup fits you best? Whether you’re leaning Meltano Open or Cloud, the documentation lays out how they stack up against each other. 💬 And if any of these sparked a question (or you’ve got a connector you’re waiting on), grab a slot here, always happy to chat.
melty 1