LogoLogo
5.2
  • Docs
  • Connector Configuration
  • Knowledge Base
  • Changelog
5.2
  • Introduction
  • Migration from 5.1
  • Overview
    • Introduction
    • Component
    • Flow
    • End User Guide
  • Component Definition
    • Basic Structure
    • Manifest
      • name
      • label
      • icon
      • marker
      • author
      • description
      • auth
      • authConfig
      • quota
      • properties
      • inPorts
      • outPorts
      • firePatterns
      • tick
      • private
      • webhook
      • state
      • localization
    • Behaviour
    • Dependencies
    • Authentication
    • Quotas & Limits
    • Configuration
    • Example Component
  • Customizing UI
    • Custom Inspector Fields
    • Custom Theme
    • Custom Strings
    • Custom API
    • Custom Component Strings
    • Custom Component Shapes
    • Custom Auth Popups
  • Appmixer hosted
    • Getting started
    • Creating Custom Components
    • Using Appmixer SDK
    • Using Appmixer API
    • Using Oauth applications
  • Appmixer Self-Managed
    • Installation
    • Getting Started
    • Custom Component: HelloAppmixer
    • Using Appmixer SDK
    • Using Appmixer API
    • Using OAuth applications
    • Installation GCP
    • System Webhooks
    • Configuration
    • Appmixer Architecture
    • Appmixer Deployment Models
    • System Plugins
  • API
    • ACL
    • Accounts
    • Apps
    • Authentication
    • Charts
    • Config
    • Data Stores
    • Files
    • Flows
    • Insights
    • Modifiers
    • People Task
    • Public Files
    • Service Configuration
    • Unprocessed Messages
    • User
    • Variables
  • Appmixer SDK
    • Introduction
    • Installation
    • Quick Start
    • Constructor
    • API Module
    • UI & Widgets
      • Flow Manager
      • Designer
      • Insights Logs
      • Insights Chart Editor
      • Insights Dashboard
      • Accounts
      • Storage
      • People Tasks
      • Connectors
      • Integrations
      • Wizard
    • Developer mode
  • Appmixer Backoffice
    • Getting Started
    • Services
    • Quotas
    • Public Files
    • System Configuration
    • Modules
  • Tutorials
    • Managing Authentication
    • Sharing Flows
    • Flows Metadata & Filtering
    • People Tasks
    • Customizing modifiers
    • Setting ACL
    • Integration Templates
    • Installing and updating modules
    • Custom Webhook Trigger
    • Appmixer Virtual Users
    • Working with outport schemas
  • Appmixer CLI
    • Appmixer CLI
    • Appmixer OpenAPI Generator
      • Getting started
      • Open API Extensions
      • Examples
  • App Registration
    • Airtable
    • Azure Cognitive Services
    • Blackboard
    • DeepAI
    • DocuSign
    • Google
    • Highrise
    • Hubspot
    • Microsoft
    • Microsoft Dynamics 365 CRM
    • Quickbooks
    • Redmine
    • Salesforce
    • Schoology
    • Screenshot API
    • ServiceNow
    • Slack
    • Trello
    • Typeform
    • Utilities
      • Email
      • Language
      • Tasks
      • Test
      • Weather
    • Xero
    • Zendesk Tickets
    • Zoho
  • Connectors
    • Connector Request
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Appmixer Backoffice

Quotas

PreviousServicesNextPublic Files

Last updated 1 year ago

Was this helpful?

You can customize the quotas used by your services through the Appmixer Backoffice. For more information about quotas, see the section. You can find the Quotas section in the left menu.

You will see a list of the existing quota definitions and a button for adding a new quota definition. What you can see here depends on what modules are installed in Appmixer. Brand new Appmixer installation without any modules will contain an empty list here. Once you add a module into Appmixer that uses quotas (appmixer.slack for example), a new row appmixer.slack will appear here.

The main purpose of this page is to give you the possibility to override the default quota rules that come with each module. Some third-party services offer the possibility to increase their quota limits by paying more money to them. When you do so, you need to tell Appmixer that it can start sending more API requests to such services. This is the way to do so.

Quota definitions that come by default are marked as non-user defined, and cannot be deleted, but they can be modified.

To create a new quota definition, click on the Add new quota definition button on the top left. This will popup a dialog like this:

You will have to provide a service name (this is the same service name defined in the component manifest):

When quotas are created or edited by you, they are marked as user-defined. These quotas can be deleted, however, if you delete a quota definition not created by you (this is, that came by default), it will revert to the default definition. If you delete a quota that was created from scratch by you, deleting it will remove it entirely.

This is how the new quota looks in the quota list. You can see the options for editing and removing quotas in the Definition column.

For editing quotas, the dialog is the same as the one for creating new quotas.

Next are the quota rules. When the dialog is opened, you will find a rule definition as an example. More detailed info about the quota rules can be found . You can use the Test button to check if your definition is valid. Once you are done, just click the Save button. You will see the new quota in the list.

Quotas and Limits
here
Quota configuration
Default quota definitions
Create new quota dialog
Service name in the manifest