Skip Navigation
Show nav
Dev Center
  • Get Started
  • Documentation
  • Changelog
  • Search
  • Get Started
    • Node.js
    • Ruby on Rails
    • Ruby
    • Python
    • Java
    • PHP
    • Go
    • Scala
    • Clojure
    • .NET
  • Documentation
  • Changelog
  • More
    Additional Resources
    • Home
    • Elements
    • Products
    • Pricing
    • Careers
    • Help
    • Status
    • Events
    • Podcasts
    • Compliance Center
    Heroku Blog

    Visit the Heroku Blog

    Find news and updates from Heroku in the blog.

    Visit Blog
  • Log inorSign up
Hide categories

Categories

  • Heroku Architecture
    • Compute (Dynos)
      • Dyno Management
      • Dyno Concepts
      • Dyno Behavior
      • Dyno Reference
      • Dyno Troubleshooting
    • Stacks (operating system images)
    • Networking & DNS
    • Platform Policies
    • Platform Principles
  • Developer Tools
    • Command Line
    • Heroku VS Code Extension
  • Deployment
    • Deploying with Git
    • Deploying with Docker
    • Deployment Integrations
  • Continuous Delivery & Integration (Heroku Flow)
    • Continuous Integration
  • Language Support
    • Node.js
      • Troubleshooting Node.js Apps
      • Working with Node.js
      • Node.js Behavior in Heroku
    • Ruby
      • Rails Support
      • Working with Bundler
      • Working with Ruby
      • Ruby Behavior in Heroku
      • Troubleshooting Ruby Apps
    • Python
      • Working with Python
      • Background Jobs in Python
      • Python Behavior in Heroku
      • Working with Django
    • Java
      • Java Behavior in Heroku
      • Working with Java
      • Working with Maven
      • Working with Spring Boot
      • Troubleshooting Java Apps
    • PHP
      • Working with PHP
      • PHP Behavior in Heroku
    • Go
      • Go Dependency Management
    • Scala
    • Clojure
    • .NET
      • Working with .NET
  • Databases & Data Management
    • Heroku Postgres
      • Postgres Basics
      • Postgres Getting Started
      • Postgres Performance
      • Postgres Data Transfer & Preservation
      • Postgres Availability
      • Postgres Special Topics
      • Migrating to Heroku Postgres
    • Heroku Key-Value Store
    • Apache Kafka on Heroku
    • Other Data Stores
  • AI
    • Working with AI
    • Heroku Inference
      • Inference API
      • Quick Start Guides
      • Inference Essentials
      • AI Models
    • Vector Database
    • Model Context Protocol
  • Monitoring & Metrics
    • Logging
  • App Performance
  • Add-ons
    • All Add-ons
  • Collaboration
  • Security
    • App Security
    • Identities & Authentication
      • Single Sign-on (SSO)
    • Private Spaces
      • Infrastructure Networking
    • Compliance
  • Heroku Enterprise
    • Enterprise Accounts
    • Enterprise Teams
    • Heroku Connect (Salesforce sync)
      • Heroku Connect Administration
      • Heroku Connect Reference
      • Heroku Connect Troubleshooting
  • Patterns & Best Practices
  • Extending Heroku
    • Platform API
    • App Webhooks
    • Heroku Labs
    • Building Add-ons
      • Add-on Development Tasks
      • Add-on APIs
      • Add-on Guidelines & Requirements
    • Building CLI Plugins
    • Developing Buildpacks
    • Dev Center
  • Accounts & Billing
  • Troubleshooting & Support
  • Integrating with Salesforce
  • Add-ons
  • All Add-ons
  • IgniteConnex Editor
IgniteConnex Editor

This add-on is operated by IgniteConnex, Inc.

APIs, ETL, Messaging, Workflows, Data Pipelines

IgniteConnex Editor

Last updated November 01, 2023

Table of Contents

  • Getting Started
  • Accessing the CG Ignite Editor
  • Monitoring and logging
  • Troubleshooting
  • Migrating between plans
  • Removing the add-on
  • Support

CG Ignite Platform is a Low-Code Application development environment built on Heroku. Use Ignite to rapidly build OData 4.0 services for Salesforce Connect consumption (amongst many other workflows). CG Ignite Editor is an add-on for managing the CG Ignite Runtime.

Getting Started

CG Ignite Editor only works with the CG Ignite Runtime. It’s a simple 1-button install to complete the installation process end-to-end.

Deploy

The CG Ignite Editor will not work with any existing applications, unless it’s an existing CG Ignite Runtime app provided through the Heroku Button install.

Using Deploy Button

Proper setup requires clicking the “Deploy To Heroku” button. Advanced users can install this Editor to an existing Ignite Runtime using the CLI.

Using Heroku CLI

$ heroku addons:create cgignite

This command only works if you’ve already installed the CG Ignite Runtime.

Accessing the CG Ignite Editor

Access the editor by navigating to Heroku Dashboard and selecting the application in question. Select CG Ignite Editor from the Add-ons menu. This authenticates with Heroku SSO and launches CG Ignite Editor cloud dashboard. From the editor dashboard, you’ll be able to manage flows within the CG Ignite Runtime app located in your Heroku account.

Access CG Ignite Editor from Heroku CLI

You may also access the dashboard via the CLI using the following example, subbing in the name of your deployed CG Ignite Runtime application:

$ heroku addons:open cgignite-cubed-98688
Opening cgignite for sharp-mountain-4005

This command only works if you’ve already installed the CG Ignite Runtime using the Heroku Button.

Monitoring and logging

You can monitor CG Ignite activity within the Heroku log-stream by using the following CLI command:

$ heroku logs -t | grep 'cgignite'

Troubleshooting

This Add-on requires our Ignite Runtime app. You must follow the installation process after clicking the deployment button.

Login Issues

If you launch the dashboard from the Add-ons menu the CG Ignite Editor will login using Heroku SSO. If you access the editor without first logging in to Heroku, you’ll land on an unauthorized page requesting that you login with Heroku.

Installation Issues

Clear your browser storage, and install the Runtime & Editor bundle using the “Deploy To Heroku” button.

Migrating between plans

Application owners should carefully manage the migration timing to ensure proper application function during the migration process.

Use the heroku addons:upgrade command to migrate to a new plan.

$ heroku addons:upgrade cgignite:newplan
-----> Upgrading cgignite:newplan to sharp-mountain-4005... done, v18 ($49/mo)
       Your plan has been updated to: cgignite:newplan

Removing the add-on

You can remove CG Ignite via the CLI:

This will destroy all associated data and cannot be undone!

$ heroku addons:destroy cgignite
-----> Removing cgignite from sharp-mountain-4005... done, v20 (free)

Before removing CG Ignite, you can export your data by using “Export” feature in the main menu.

Support

All CG Ignite support and runtime issues should be submitted via one of the Heroku Support channels. Any non-support related issues or product feedback is welcome at support@cgignite.com.

Keep reading

  • All Add-ons

Feedback

Log in to submit feedback.

Zara 4 Insight Hub (formerly BugSnag)

Information & Support

  • Getting Started
  • Documentation
  • Changelog
  • Compliance Center
  • Training & Education
  • Blog
  • Support Channels
  • Status

Language Reference

  • Node.js
  • Ruby
  • Java
  • PHP
  • Python
  • Go
  • Scala
  • Clojure
  • .NET

Other Resources

  • Careers
  • Elements
  • Products
  • Pricing
  • RSS
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku Blog
    • Heroku News Blog
    • Heroku Engineering Blog
  • Twitter
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku
    • Heroku Status
  • Github
  • LinkedIn
  • © 2025 Salesforce, Inc. All rights reserved. Various trademarks held by their respective owners. Salesforce Tower, 415 Mission Street, 3rd Floor, San Francisco, CA 94105, United States
  • heroku.com
  • Legal
  • Terms of Service
  • Privacy Information
  • Responsible Disclosure
  • Trust
  • Contact
  • Cookie Preferences
  • Your Privacy Choices