Support tickets allow you to report an issue, ask questions about integrator.io, resolve billing issues, or get help with Integration Applications. By submitting a ticket, we can help you with any number of system, integration, connection, or flow issues.
- Submit a support ticket or provide feedback
- Submit an integrator.io ticket
- Submit an Integration App ticket
Submit a support ticket or provide feedback
Not sure if you should submit a support ticket or provide feedback? Support tickets are created when you have a technical issue with your integrations. This could be reflected by errors when creating or editing flows, malfunctioning or non-functioning integrations, or other system-breaking issues.
In order to submit a support ticket, you must navigate to the Celigo Help Center. Then click Submit ticket at the top of the screen.
On the other hand, providing feedback is appropriate when you want a new feature, want changes to an existing feature, or want to submit general feedback about integrator.io.
Note: Choosing the correct category affects your entire support ticket process. For example, if you have an issue with the Shopify - NetSuite Integration App but select integrator.io, your ticket won't reach the proper support team (Shopify). Instead, it will be routed to the integrator.io team, and they will have to transfer your ticket to the Shopify team.
You can choose a category using the dropdown or by clicking a tile. There are three types of integrator.io tiles:
- Integrator.io: This covers any troubleshooting questions you may have about integrator.io.
- Legacy integrator: This covers the legacy version of integrator.io, which is no longer supported.
- General, billing, other: This covers any general, billing, or other questions about integrator.io.
Note: This section is meant for questions about integrator.io as a platform, not for integrator.io troubleshooting help. To get troubleshooting help, use the integrator.io category.
There are multiple subcategories you can use to further narrow down your topic. Remember, narrowing down the topic can help our Support team resolve issues quickly. The subcategories are:
- API (api.integrator.io)
- Audit Log
- Flow Builder
- General Help
- Hooks / Wrappers / Stacks
- IO Managed Integrations
- On-Premise Agent
- Product Defect / Bug
- Product Enhancement;
- Recycle Bin
- Roles and Permissions
- Sample Data
- Security / Privacy
- SmartConnector Builder
- Subscription / Licensing
- Template Zips
- Transfer Ownership
Regardless of the subcategory you choose, you still need to provide basic information about your instance of integrator.io.
Required fields must be completed to submit a ticket.
- Subject: A quick summary of your issue.
- Description: An in-depth description of your issue.
- Do you currently have an open project with Celigo to implement this integration?: This determines if you have any open projects with Celigo to implement the integration you're submitting a ticket for.
- Environment: In what environment is your issue occurring?
- Sandbox: Your testing environment.
- Beta: A beta or secondary testing environment.
- Production: Your production or "live" environment.
- Integrator.io Subcategory: Select one of the subcategories listed above.
- Error messages (can be provided in the description).
- Integration and flows encountering the issue.
- Any attempted resolutions of the issue.
- Any community questions you've posted or help center articles you've reviewed.
Optional fields are not required, but assist Support in understanding and solving the issue.
- CC: Other co-workers you would like to include in the support ticket (by including their email).
- Urgency: The priority or level of concern for the issue.
- Low: A low priority issue is important, but doesn't need to be resolved immediately. Low priority issues are usually not breaking your integrations.
- Normal: A normal priority issue is important, but is not breaking major parts of your integrations.
- High: A high-priority issue is important and might be preventing your integration from performing at its best.
- Urgent: An urgent issue is important and is nearly or completely stopping your integrations from performing as expected.
- Preferred Time Zone: Your local time zone. This helps schedule meetings appropriately.
- integrator.io connected applications: Any applications connected to integrator.io that might be related to the issue.
- Integration Name: The name of your erroring integration.
- Flow Name: The name of your erroring flow.
- Celigo Partner: If you are or are not a Celigo partner.
- Attachments: Any screenshots or videos of your errors.
Note: Include as many images or videos of your errors as possible. When submitting an image, ensure that the entire screen is visible rather than just the error. This will help provide context for the support team.
This subsection is for any general questions about integrator.io, to resolve billing errors, or for any other miscellaneous questions you might have.
Note: This section is meant for questions about integrator.io as a platform, not for integrator.io error or troubleshooting help. To get error or troubleshooting assistance, use the integrator.io category.
Integration apps represent fully functional pre-built integrations that you can install into your integrator.io account from the integrator.io Marketplace. They include an installer, an uninstaller, and a settings interface. Developers can push updates at any time for any connector to their entire install base. Integration apps are mostly made up of code that uses the integrator.io API to interact with a user’s account. All components created in a customer’s account are tagged with the integration app’s _id (via the _connectorId field). An integration app can modify only those components tagged with its own _id. The schema primarily serves the purpose of listing an integration app in the integrator.io marketplace with a description, imageURL, websiteURL, and so forth.
The Integration Apps we provide are:
- NetSuite standard integrations
- Amazon MCF
- Amazon Seller Central
- Cash Application Manager (IO)
- Cash Application Manager (V2)
- Magento 1 (V4 IO) (by Nova Module)
- Magento 2
- Salesforce (IO)
- Salesforce (V2)
- Salesforce Commerce Cloud
- Silicon Valley Bank
- Vendor Payment Manager
- NetSuite to NetSuite operations (by Nova Module)
- Auto-Bill Sales Orders in NetSuite
- Auto-Create Customer Deposit
- NetSuite integrations (by Nova Module)
- DCL (3PL)
- Facebook Catalog Manager
- Ramp Logistics
- NetSuite Connector (by Nova Module)
- Salesforce integrations
The required and optional fields are identical to those for integrator.io. However, some integrations might have additional required fields, such as Categories. These categories vary by Integration App and can be related to the type of flow, import, or export.