Nimbus Intelligence Connectors
  • Nimbus Intelligence Connectors
  • Connector Applications
    • Getting Started
    • Available Connectors
      • ActiveCampaign
      • Atlassian Confluence
      • Atlassian Jira
      • Asana
      • Capsule CRM
      • Elapseit
      • Entrace
      • Exact Online
      • Fatture in Cloud
      • FreeAgent
      • Freshdesk
      • Freshservice
      • Freshsales
      • Gripp
      • Holded
      • HubSpot
      • KNMI
      • Mailchimp
      • Microsoft Dynamics 365 Business Central
      • Monday
      • Personio
      • QuickBooks Online
      • Shopify
      • SurveyMonkey
      • WordPress
      • MongoDB
      • Tableau Server
    • Releases
    • Limitations and Known issues
    • Frequently Asked Questions
  • Nimbus Intelligence
    • About Us
    • Contact Us
    • Support
Powered by GitBook
On this page

Was this helpful?

  1. Connector Applications

Limitations and Known issues

We are continuously working on improving our connectors!

Limitations

Only one task can be configured per connection

For now, only one task can be set up per connection.

Workaround

If you need different refreshing schedules for different endpoints, create different connections with the same credentials (but different endpoint selection, if you wish so) and configure different tasks for them.

Leaving the App / App becoming Idle

Leaving the app during data fetching using the "Fetch Data" button or letting the app idle may cause incomplete data loading.

Workaround

Stay in the app while fetching data or use tasks, which are not affected by this behavior.

Wrong Credentials
  • Limitation: If you enter incorrect credentials in the connection script, the log table may incorrectly show success. This doesn't apply to OAuth authentication, which will report an error.

  • Workaround: Always provide the correct credentials and use the "Test Connection" button to verify before fetching data or setting tasks.

Last updated 1 year ago

Was this helpful?

Page cover image