A universal guide outlining the common steps involved in setting up any OAuth2 application, including registering your application, obtaining client credentials, and defining redirect URIs.

• Sign-in to to your ActiveCampaign account. Once you are logged in, locate the "Settings" option. This can be found in the bottom left corner of the homepage.

• Within the settings page, you will see a section labeled 'Developer'. Click on this section to navigate to the Developer page. On the 'Developer' page, you will see your API URL and your API key.

• use the API Key to authenticate ActiveCampaign components in the Appmixer Designer.

Authentication

Lambda, S3 and SNS

To authenticate with AWS services Lambda, S3, and SNS, you need to provide Access Key Id and Secret Access Key. You can create a new user in the AWS IAM console (https://console.aws.amazon.com/iam/home) and assign the necessary permissions to that user.

The neccessary permissions depend on the services and components you want to use. For example, if you want to use the New S3 Object component, you need to assign the AmazonS3ReadOnlyAccess policy to your user. If you want to use the Send SNS Message component, you need to assign the AmazonSNSFullAccess policy.

Sign up with Airtable:

Specify Table name

Now the Airtable workspace/base is prepared. Let's configure the OAuth app.

The last step is to configure clientId and clientSecret in the Appmixer Backoffice for appmixer:airtable

The Anthropic Claude connector (AI > Anthropic Claude: AI Agent, Send Prompt, Transform Text to JSON, List Models, Make API Call) authenticates with an Anthropic API key. Each user enters their own key when connecting an account in the Designer, so there is no app to register with Anthropic.

1. Sign in to the Claude Console at (formerly console.anthropic.com). Create an account if you do not have one.

2. Open Settings > API keys ().

The Appmixer Arcmira connector (Find Transcripts, Resolve Entity, Make API Call) uses API key authentication. You do not need to register an OAuth app with Arcmira. Each user creates an API key in their Arcmira account and enters it when they connect Arcmira in Appmixer.

1. Create an API key

1. Sign in to Arcmira. Create an account if you do not have one. New accounts start on the Free plan.

2. Open Dashboard → API keys.

3. Click Create key.

4. Copy the key. It starts with arc_sk_. Arcmira shows the secret only once, so store it somewhere safe.

Dashboard keys carry the scopes read, monitors:write, trackers:write and recommendations:read. Find Transcripts and Resolve Entity only need read. Make API Call can also change monitors and trackers, as far as the key's scopes allow.

Arcmira also lets you get a key without a browser, through its sign-up API. See in the Arcmira documentation.

When you add an Arcmira component to a flow, Appmixer asks you to connect an account. Paste the key into the API Key field.

Appmixer sends the key as a bearer token (Authorization: Bearer <key>) to https://api.arcmira.com/v1. To check the key, it calls GET /v1/me, which is free and works even when the account has no credits left. The connection is named after the masked email of the key's owner (or the key label). For a team account, the team name is shown in front of it.

Make API Call only sends requests to https://api.arcmira.com/v1. It rejects other hosts, so the key is never sent anywhere else.

Arcmira limits requests per API key in a 60-second window: 60 on the Free plan, 240 on paid plans and 600 on Enterprise. The connector queues requests to stay at 60 requests per 60 seconds per connected account, so it stays under the limit on every plan.

• 401 when connecting: check that you copied the whole key (arc_sk_…) and that it has not been disabled on the API keys page.

• 402 errors when running a flow: the account has run out of credits or reached its on-demand budget. Check the plan and usage in the Arcmira dashboard.

• 403 insufficient_scope from Make API Call: the key does not have the scope that the request needs (for example monitors:write

Configuration ID: appmixer:arcmira. For how to set connector configuration values, see .

You do not need any Backoffice configuration to authenticate, because every user enters their own API key. There is one optional key:

• outputFilePrefix: optional. A prefix for the names of CSV files created when Find Transcripts runs with the Store to CSV file output type. Files are named <prefix>-<component label in the flow>.csv. The default is arcmira-objects-export.

1. Create Asana account

Sign up with Asana: https://app.asana.com

2. Register OAuth app

To create an OAuth app with Asana, follow the oficial documentation: https://developers.asana.com/docs/oauth#register-an-application.

Take note of the application's client ID and the client secret (which should be protected as a password)

You will need to specify the App name and Redirect URL in this step.

• The App name can be anything you want.

• The Redirect URL should be the URL where Asana will redirect the user after they authorize your app. This depends on your environment, usually in the following format: https://api.qa.appmixer.com/auth/asana/callback

Set clientId and clientSecret into Appmixer Backoffice.

The last step is to configure clientId and clientSecret in the Appmixer Backoffice for appmixer:asana

HTML to JSON Converter

Description Convert an HTML table file into a JSON file.

Input Parameters

• fileId (string) - The ID of the file to be converted.

Output Parameters

• fileId (string) - The ID of the newly created JSON file.

• fileName (string) - The name of the converted JSON file.

XLSX2JSON Component

Description: Convert an XLSX (Excel 2007+ XML format) file to JSON.

Input Parameters:

• fileId (string, required): The ID of the file to be converted.

Output Parameters:

• fileId (string): The unique ID of the converted JSON file.

• fileName (string): The name of the generated JSON file.

Log In to JotForm

• Go to the JotForm website.

• Log in with your JotForm account credentials.

Generate a New API Key

• Navigate to Account Settings: Click on your avatar/initials in the top right corner of the page. Choose "Settings" from the dropdown menu. Or go directly to the https://jotform.com/myaccount/api

• Here, you might see a list of existing API keys if you've created any before. To generate a new one, click the “Create New Key” button

Use the API key in the Appmixer

• In the authentication pop-up enter your API key.

Setup Mailchimp account

Sign up with Mailchimp: https://mailchimp.com/

2. Register OAuth app

Now you need to add an OAuth application. Navigate to: Profile > Extras > Registered apps.

Click on the "Register an app" button.

Specify client details

Generate client secret

Now save the OAuth client and copy the client ID and secret. You will need them later.

Set clientId, clientSecret and subdomain into Appmixer Backoffice.

The last step is to configure clientId and clientSecret in the Appmixer Backoffice for appmixer:mailchimp connector.

Authentication

To authenticate Imperva connector, an API Key is required. To obtain this key, log in to your Imperva account and navigate to Account > My Profile > API Keys. Click on "Add API Key" to generate a new key. Enter a name (and optionally otherparameters) for the API Key and click on "Create".

Take note of the API ID and API Key. You will need these to authenticate the connector.

You can also view the API Key details in the API Keys section.

In the Imperva connector authentication window, use your Imperva API ID and API Key to log in.

Configuration

There are three optional configuration parameters for the SetBlockIPRule action of the Imperva connector. See the table below for more information.

• OpenAI Account: The first thing you need to do is have an OpenAI account. You can sign up for free.

• After signing up, go to https://platform.openai.com/api-keys.

• Create a New API Key: You would find a button or link labeled "Create a new key" or "Generate API keys". Click on it.

• Keep this key safe and secure. It should not be shared with anyone or exposed in client-side code, as it could be used to misuse your OpenAI services.

• use the API Key to authenticate OpenAI components in the Appmixer Designer.

Sign-up at DeepAI

Visit https://deepai.org and sign-up:

Copy api-key from your profile dashboard:

Set the API key via the the Backoffice Connector Configuration page:

And then add you own apiKey value:

In order to offer the Azure Cognitive Services components to your customers, you have to set an Azure key and endpoint through the Backoffice first.

1. Create Pipedrive account

Sign up with Pipedrive: https://www.pipedrive.com

2. Obtain API key

Navigate to My Account -> Personal Preferences -> API. Copy the API token.

Use the copied token as apiKey when connecting Pipedrive components in Appmixer.

1. Create Monday account

Sign up with Monday: https://auth.monday.com/users/sign_up_new

2. Obtain API key

Navigate to your Monday Developer Center -> My access tokens. Create a new token and copy it.

Use the copied token as apiKey when connecting Monday components in Appmixer.

Cloudflare WAF integrations allows you to actively block attacker IP by using Cloudflare WAF infrastructure.

Authentication

Cloudflare WAF connector support authentication via Account API Token or User API Token

Account API Token

To create the Account API Token, go to the Manage Accounts > Account API Tokens, click on "Create Token". On the next screen, select the "Create Custom Token" option.

Name the token and select the permission:

• Account | Rule Rulesets | Edit

User API Token

To create the User API Token, go to the Profile > API Tokens, click on "Create Token". On the next screen, select the "Create Custom Token" option.

Name the token and select the permission:

• Account | Rule Rulesets | Edit

In the Cloudflare connector authentication window, use your API Token to log in.

Go to the Apps and Keys page (you can also get there from the Docs)

Add a new app:

Get the ClientId, ClientSecret and set the redirect URI:

clientId: Integration Key

clientSecret: Secret Keys

set the Redirect URI to https://[YOUR_API_BASE]/auth/docusign/callback, for example https://api.appmixer.com/auth/docusign/callback

And set the clientId, clientSecret to the service configuration in the Backoffice.

Get your consumer key and secret

Log in to your Schoology server. Look at the top navigation bar and go to Tools > School Management.

In the new screen, click on Integrations in the left menu. Now click on the API tab. You should see your consumer key and secret. The secret is hidden, so you have to use the Reveal Existing Secret option.

Configure the authentication values in Appmixer

Log into the Backoffice and go to the Services section. Add a new service configuration named appmixer:schoology. After it is created, add the following configuration values:

Here is the explanation for each value:

• baseUrl: The API base URL. Usually is https://api.schoology.com/v1, but there are some cases where it could be different.

• consumerKey and consumerSecret: The consumer key and secret we got from the Schoology server.

• domain: The subdomain part from your server. For example, if your server URL is https://example.schoology.com, then the domain value is just an example.

You will need to create a new Redmine installation. Go to https://www.redmine.org/projects/redmine/wiki/RedmineInstall and follow the instructions. Alternatively, you can use a Docker image: https://hub.docker.com/_/redmine or a hosted solution.

Once you have your Redmine application make sure you have the REST API enabled. Go to Administration -> Settings -> API and check the "Enable REST web service" option.

After that, you will need to create a new API key. Go to Administration -> Users -> Edit user and create a new API key.

You will enter this API key and also the URL of your Redmine installation in when connecting each Redmine component.

1. Create Freshdesk account

Sign up with Freshdesk: https://www.freshdesk.com

2. Obtain API key

Navigate to Profile Settings -> API. Copy the API token on the right side. If you don't see the API key, please refer to the Freshdesk documentation for more information.

Use the copied token as API key along with Domain when connecting Freshdesk components in Appmixer. In this example the domain is acme-help and the API key is the copied token.

Unfortunately, since August 20, 2018 Highrise no longer accepts signups.

We keep the module in Appmixer for the older customers who have their Oauth2 application. If you are a new Appmixer customer, you won't be able to create the OAuth2 application and therefore use the Highrise module. In that case, you should remove it from the platform.

User-Agent

Requests to the Highrise API contain headers with User-Agent property. This is set by default to Appmixer, but it can be overwritten using Backoffice:

Appmixer offers a built-in component for taking Screenshots.

It uses https://screenshotapi.net/ API. If you want to have this module on the platform you have to create your own Screenshot account and set the API token in the Backoffice.

When creating Typeform Oauth2 application (https://admin.typeform.com/account#/section/apps), you can choose between access tokens that do expire in a week and access tokens that do not expire.

The token expiration is new in Typeform. Appmixer components before version 4.2 cannot handle it.

If you're registering the Oauth application for version 4.2 or newer, you can decide if you want to use tokens that do expire or not. If you decide to go with Unlimited then you don't have to set anything in the Backoffice, it is the default behavior. On the other hand, if you want to use tokens that expire, you have to go to the Backoffice and set the useRefreshToken to true for the appmixer:typeform service.

Then you can use the One Week configuration.

Since version 4.2.1 you can configure the string that appears on the Trallo Oauth page.

If you don't do this, the Oauth page will show Appmixer by default.

Appmixer AI utilities allows you to introduce AI functionality in your integrations, automations or simply extend your product with AI capabilities via Appmixer's No-Code Studio.

After installing the appmixer.utils.ai module, go to the Backoffice to configure the OpenAI apiKey for the module:

Additionally, you can also override the default OpenAI models for the SendPrompt (default is "gpt-4o") and GenerateImage (default is "dall-e-3") components:\

• First, you'll need to create an account on the Twilio website.

• After signing up, go to https://console.twilio.com/

• Copy the Account SID and Auth Token from the "Account Info". Alternatively you can navigate to the "API Keys & Tokens" section, SID and Auth Token are available there.

• use the Auth Token and Account Token to authenticate the Twilio components in the Appmixer Designer.

Overview

The HTML to CSV Converter component allows you to transform an HTML table file into a CSV format. This is useful for extracting structured data from HTML documents into a tabular format.

Input Parameters

Output Parameters

Instructions

1. Select the HTML File:

   • Provide the fileId of the HTML document that contains a table.

2. Processing:

   • The component extracts the table data from the HTML file and converts it into a structured CSV format.

3. Retrieve Output:

   • The component returns a new file with fileId and fileName in CSV format.

Account

You'll need a Snowflake account. If you don't have one, you can sign up for a free trial on the Snowflake website.

Obtain Credentials and Configuration

You will need the following details to connect to your Snowflake database:

• Account Name: This is often part of your Snowflake URL. You can find it in the Snowflake web interface after logging into your account.

• Username: The username of the Snowflake user account you wish to use.

• Password: The password for that Snowflake user.

• Database Name: The name of the database you want to connect to.

• Warehouse: The name of the virtual warehouse to use for running queries.

How to Find This Information:

• Account:

  • Your account identifier is usually part of your Snowflake URL.

  • When you log into Snowflake, the URL looks like https: //abc12345.us-east-1.snowflakecomputing.com.

  • Here, abc12345.us-east-1 is your account identifier.

• Username and Password:

  • The credentials you use to log into the Snowflake web interface.

• Database and Warehouse:

  • After logging into Snowflake, navigate to the Databases and Warehouses tabs to see available options.

  • Choose the appropriate database and warehouse for your needs.

The Appmixer Azure DevOps connector uses Microsoft Entra ID (Azure AD) OAuth 2.0 for authentication. You need to register an application in the Azure portal.

1. Register an Application in Azure Portal

Go to the Azure portal - App registrations and click + New registration.

• Name: A name for your application (e.g. "Appmixer Azure DevOps").

• Supported account types: Select Accounts in any organizational directory (Any Microsoft Entra ID tenant - Multitenant).

• Redirect URI: Select Web and set it to your Appmixer callback URL, e.g. https://api.YOUR_SUBDOMAIN.appmixer.cloud/auth/azuredevops/callback.

Click Register.

2. Get Application (Client) ID

After registration, you will be taken to the app's Overview page. Copy the Application (client) ID - this is your clientId.

3. Create a Client Secret

1. In the left menu, go to Certificates & secrets.

2. Click + New client secret.

3. Add a description and select an expiration period (use the longest available).

4. Click Add.

5. Copy the Value of the newly created secret immediately - this is your clientSecret. It will not be shown again.

4. Configure API Permissions

1. In the left menu, go to API permissions.

2. Click + Add a permission.

3. Select Azure DevOps.

4. Select Delegated permissions.

5. Check user_impersonation.

6. Click Add permissions.

The final set of permissions should include:

5. Configure Appmixer Backoffice

Go to the Connector Configuration section in the Appmixer Backoffice. Find or add the appmixer:azuredevops connector and set the following values:

• clientId: The Application (client) ID from the Azure portal.

• clientSecret: The Client Secret Value from the Azure portal.

Overview

The SetVariable Component assigns variables dynamically based on input type and value. It allows storing values in various formats such as text, numbers, dates, booleans, and files.

Usage

Input Ports

Output Ports

Supported Variable Types

• Text (text) – Stores a string value.

• Textarea (textarea) – Stores a longer text value.

• Number (number) – Stores a numeric value.

• Date-Time (date-time) – Stores a date and time.

• Boolean (toggle) – Stores a true/false value.

• File (filepicker) – Stores a selected file reference.

Instructions

1. Provide Variables

   • Send an object containing variable names, types, and values to the in port.

2. Processing Variables

   • The component assigns the variables dynamically based on their types.

3. Retrieve Output

   • The processed variables are sent as an object through the out port.

Notes

• Flexible Variable Storage: Supports multiple data types for dynamic variable assignments.

• Useful for Workflow Automation: Allows temporary storage of values for later processing.

• Outputs in Key-Value Format: The output is structured as an object containing assigned values.

Description

Convert a CSV file to XLSX (Excel 2007+ XML Format).

Input Parameters

Output Parameters

Instructions

1. Provide File ID:

   • Select the CSV file to be converted using its fileId.

2. Processing:

   • The component processes the file and converts it into an XLSX format.

3. Retrieve Output:

   • The converted file is returned with a fileId and fileName for further use.

Overview

The OnStart Component is a trigger that fires once when the flow starts. It emits a timestamp indicating when the flow was initiated.

Usage

Output Ports

Output Data for out Port

Instructions

1. Automatic Trigger

   • The component automatically fires when the flow begins execution.

2. Start Time Emission

   • Outputs a started timestamp that can be used for logging, tracking, or scheduling purposes.

Notes

• One-Time Execution: Triggers only once per flow execution.

• Useful for Logging: Can be used to capture flow start times for analytics or debugging purposes.

Overview

The DataUri2File component converts a Data URI into a file. It extracts the file content and metadata from the Data URI and generates a downloadable file.

Input Parameters

Output Parameters

Instructions

1. Provide a Data URI

   • Input a valid Data URI string that represents a file.

2. Specify a File Name (Optional)

   • Enter a desired file name with or without an extension.

   • If omitted, the extension is inferred from the file type.

3. Processing

   • The component extracts the file content from the Data URI and saves it as a downloadable file.

   • Returns the fileId and fileName of the newly created file.

Overview

The Counter Component maintains an internal counter that increments with each received message. It can also be reset to a specified value.

Usage

Input Parameters

Input Ports

Output Ports

Instructions

1. Set Initial Value and Increment

   • Configure the count parameter for the starting value.

   • Set increment to define how much the counter increases or decreases.

2. Increment Behavior

   • Each time a message arrives at the item port, the counter increases by the increment value.

3. Reset Counter

   • Sending a message to the reset port resets the counter to the specified value or its initial value if no value is provided.

Notes

• Supports both increment and decrement operations.

• State is maintained: The counter retains its value across executions until reset.

• Useful for tracking counts in loops, event occurrences, or rate-limiting scenarios.

The Mistral AI connector (AI > Mistral AI: Send Prompt, Describe Images, Generate Embeddings, Extract Document Text, Create Transcription, Create Speech, Moderate, List Models, List Voices, Make API Call) authenticates with a Mistral API key. Each user enters their own key when they connect an account in the Designer, so you do not need to register an app with Mistral.

Get an API key

1. Sign in to Mistral AI Studio at console.mistral.ai. Create an account if you do not have one.

2. In the left sidebar, open API Keys.

3. Click Create new key.

4. Enter a Name for the key and set an Expiration date. Choose any Connector access scope. The scope only controls access to Mistral's own Connectors, and the Appmixer connector does not use them.

5. Click Create new key and copy the key. Mistral shows the full key only once.

6. In the Appmixer Designer, connect a Mistral AI account and paste the key into the API Key field. Appmixer checks the key by listing the available models.

New accounts start in Free mode. Free mode gives API access without a credit card, but usage and rate limits apply. For production use, choose a paid plan in Studio. Requests over the workspace limits fail with rate-limit errors.

Backoffice configuration

You do not need any Backoffice configuration. The connector reads one optional key that changes how it caches lists.

Configuration ID: appmixer:ai:mistral. See Connector Configuration for how to set it.

• listCacheTTL – optional. How long, in milliseconds, the connector caches the model list and the voice list (used by List Models, List Voices and the model and voice selectors in the components). Each API key has its own cache. Default: 120000 (2 minutes).

Create Blackboard App in the Developer portal

The first thing you need is an app created in the developer portal. Navigate to https://developer.blackboard.com and signup for an account. When you are logged in, you can see a dashboard with a list of your applications and a button to create a new one:

Note that listed applications have an Application ID. We will need it when we register our application in the blackboard instance. Click on the + button to create a new application. A simple form appears with your Application name and description inputs, and a domains input, for your domains. After you fill in the fields, create the new application.

Register your application on Blackboard

Self-managed instances

Log in with admin privileges, and go to the System Admin tab in the top menu. After that, look under Integrations for REST API Integrations:

Next, you will see a list with all your API Integrations. Click on Create Integration to add a new one:

After that, you will show a small form. One of the inputs is the Application ID which as we showed in the first step, is available in the applications list at the developer portal. Next, browse and select a user. We recommend using the same user you are logged in with. On the End User Access and Authorized To Act As User, select Yes in both options. After that click on Submit to finish the registration.

Configure the Backoffice

Finally, we need to set the OAuth clientId and clientSecret in the to finish the integration. To obtain these values, go to the applications list in the developer portal. Find your application and click on the 3 dots at the end of the row. Then click on the Manage Keys option:

After you will see a list of your application keys. Click on the + sign to create a new key. Your key will be created and its information will be shown to you:

Be sure to store this information somewhere safe, as you won't be able to get it again.

Next, log into the Backoffice and go to Services. Next create a configuration for appmixer:blackboard. Finally, add your Application ID as clientId and Secret as clientSecret. Also set serverUrl to your instance URL:

And you are done! You are ready to use the Blackboard module.

Cloudflare List Integrations allow you to manage IP lists efficiently. You can add or remove IPs from Cloudflare IP Lists and specify the TTL (Time To Live), which automatically removes the IP after a set time period.

Custom IPs list

You can access custom lists in your Cloudflare account by navigating to Manage Account > Configurations > Lists. Cloudflare Lists connector only supports IP lists.

Authentication

Cloudflare Lists connector support authentication via Account API Token, User API Token, or Global API Key (deprecated).

Account API Token

To create the Account API Token, go to the Manage Accounts > Account API Tokens, click on "Create Token". On the next screen, select the "Create Custom Token" option.

Name the token and select the permission:

• Account | Account Filter Lists | Edit

User API Token

To create the User API Token, go to the Profile > API Tokens, click on "Create Token". On the next screen, select the "Create Custom Token" option.

Name the token and select the permission:

• Account | Account Filter Lists | Edit

Global API Key (deprecated)

My Profile > API Tokens. Click on "View" to get the token:

In the Cloudflare connector authentication window, use your Cloudflare account email and the Global API Key or your API Token to log in. Please note that when you use the API Token (User or Account), don't enter the email, just leave the email input empty.

Access the Dropbox App Console

• Open the Dropbox App Console.

• Log in with your Dropbox account credentials.

Create OAuth app

Settings page

• Set the Redirect URI to https://[YOUR_API_BASE]/auth/dropbox/callback, for example https://api.appmixer.com/auth/dropbox/callback

• To allow additional users, click on "Enable Additional Users.

• Configure the App Key as clientId and the App Secret as clientSecret in the service settings within the Backoffice, under the configuration ID appmixer:dropbox.

• To learn more about configuring connectors, please visit the Connector Configuration section.

Permissions page

Ensure that the following permissions are selected:

• account_info.read

• files.content.read

• files.content.write

• files.metadata.read

Create Facebook OAuth Application

1. Visit https://developers.facebook.com/ and create a new OAuth application (or use your existing one).

2. Add Facebook Login for Business and Marketing API products.\

   
3. Copy the App ID and App Secret a and paste it to your Appmixer Backoffice -> Connector Configuration page under the appmixer:facebookbusiness configuration ID as clientId and clientSecret, respectively:\
4. Add your Appmixer tenant domains as your App domains:\

   Note: replace YOUR_TENANT with the name of your hosted tenant. If you're a customer on an Appmixer Self-Managed plan, you can have a completely custom domains that Appmixer runs on. Use your own domains instead.

5. Set the OAuth redirect URI under Facebook Login for Business / Settings to https://api.YOUR_TENANT.appmixer.cloud/auth/facebookbusiness/callback:\

Register OAuth app

• You need to start by creating a new app on the LinkedIn Developer platform. Visit https://developer.linkedin.com/ and log into your account. Once logged in, navigate to "MyApps", then click on "Create App". Fill in all necessary information like app name, app logo, app description, app privacy policy URL etc. You also need to fill the "Associated LinkedIn page". This is the LinkedIn page that will be associated with the app. If you don't have a LinkedIn page, you can create one by clicking on the "Create a LinkedIn Page" link.

• Navigate to the "Auth" section where you will find OAuth 2.0 settings. Here, you can set the "Authorized Redirect URLs". Take note of the application's client ID and the client secret (which should be protected as a password)

  You will need to specify the Redirect URL in this step.

  The Redirect URL should be the URL where LinkedIn will redirect the user after they authorize your app. This depends on your environment, usually in the following format: https://api.ACME.com/auth/linkedin/callback

• Configure scopes: Navigate to the "Products" section, request access to "Share on LinkedIn" and "Sign In with LinkedIn using OpenID Connect", once approved (it's instant approval), you will be able to see them on the top of the screen:

Appmixer Backoffice.

Set clientId and clientSecret into Appmixer Backoffice for appmixer:linkedin

Verification

Verification will enable scopes to be used in the LinkedIn Appmixer connector: "Advertising API", "Lead Sync API", "Conversions API" and "LinkedIn Ad Library". These scopes are not used in the current version of the LinkedIn connector, therefore it's not required. You can still perform the verification by sending the verification link generated in the "Settings" tab to the Super Admin of the page associated with the App.

Process estimated time: instant approval.

Register an OAuth2 application in a similar way as usual Microsoft Azure App with few changes:

• you don't need to configure OneDrive file picker

• configure API permissions for Dynamics 365, see below

Go to the API permissions section:

Choose Dynamics CRM:

Delegated permissions:

The final set of permissions:

Creating CRM Dataverse environment

In order to use the Microsoft Dynamics 365 CRM connector, you'll need a Dataverse environment alongside your Microsoft account. You can review your environments in PowerPlatform administration. If you don't have any environment there, you can start with a trial. From the list of available apps, select Dynamics 365 Sales. Once you complete the sign-up process, the CRM environment will be created.

Once created you can view details of the environment and see Environment URL address which you will need when connecting a Microsoft Dynamics 365 CRM component to your account.

Note that in order to interact with Lead entities, you'll need to install Sales module into your Dataverse environment. Some entities like Contact or Account come with a Dataverse environment by default, but it is not the case for Lead entity.

Addition configuration

Microsoft Dynamics 365 CRM connector has additional settings when it comes to caching Dataverse environment schema and data. These settings can be configured in the Backoffice the same way as clientId or clientSecret:

• listLookupOptionsCacheTTL - Cache TTL for inspector variables in milliseconds. Default value 1 minute. Determines how long the values of various Lookup fields are stored in Appmixer cache. This affects values fetched into select boxes in the inspector for fields like Currency, Contact, etc.

• listOutportCacheTTL - Cache TTL for outports in milliseconds. Default 1 hour. Determines how long Appmixer caches the structure of the Dataverse instance (environment) for output ports. In case you add a new table or change an existing table (eg. by changing column type), this is the time you need to wait before the changes are propagated into components outPort schema.

• listInspectorCacheTTL - Cache TTL for inspector in milliseconds. Default 1 hour. Similar to listOutportCacheTTL. Determines how long Appmixer caches the structure of the Dataverse instance (environment) for the inspector. In case you add a new table or change an existing table (eg. by changing column type), this is the time you need to wait before the changes are propagated into the component's inspector.

Access the Twitter App Console

• Navigate to the Twitter Developer Platform and sign up if you haven't already.

• You might be required to apply for a developer account where you'll need to provide some information about your intended use of Twitter’s API.

Create OAuth app

• After logging in to your Twitter Developer account, navigate to the Developer Dashboard.

• Twitter should automatically create a default project and application for you. If it doesn't, click "Create Project" and follow the prompts to set up a new one. After creating the project, you'll be able to create an application. Navigate to your project and select "Add App."

• Update application details, such as the name, description, and icon, by clicking the "Edit" button. Next, configure the authentication settings.

User Authentication Settings

• Set the "App permissions" to "Read and write" and "Type of App" to "Web App"

• Set the Redirect URI to https://[YOUR_API_BASE]/auth/twitter/callback, for example https://api.appmixer.com/auth/titter/callback

Keys and Tokens

• Get the Client Id and Client Secret from the Keys and Tokens page

• Configure the App Key as clientId and the App Secret as clientSecret in the service settings within the Backoffice, under the configuration ID appmixer:twitter.

• To learn more about configuring connectors, please visit the Connector Configuration section.

Register OAuth2 app

Go to the Discord Developer Portal: https://discord.com/developers/applications and create a new Application.

1. Click “New Application”

2. Give it a name, accept their Terms of Service and click “Create”

3. Open your new application

Basic Information

To obtain your OAuth credentials, go to OAuth2 tab:

• Client ID: shown on the “Client information” card as “Client ID”

• Client Secret: click “Reset Secret” to generate a secret and copy it

You’ll paste these into the Appmixer Backoffice later.

You must add the redirect/callback URL so Discord can return users to Appmixer after authorization.

• Go to OAuth2 tab

• In “Redirects”, add your Appmixer URL. Example:

  https://api.YOUR_SUBDOMAIN.appmixer.cloud/auth/discord/callback

Note: Replace YOUR_SUBDOMAIN with your actual Appmixer subdomain. The path “/auth/discord/callback” follows the same pattern as other Appmixer connectors.

To make the events (sending messages, reacting to events) be from a bot, add one:

• Click “Reset Token” to reveal the Bot Token and copy it

Keep the token secure. You’ll paste it in the Backoffice as well.

Check the settings below in Authorization Flow, recommended set up is:

• Public Bot: ON

• Requires OAuth2 Code Grant: ON

• Server Members Intent: ON

Rest can be turned off.

How you configure scopes:

• Installation → Default Install Settings:

  • User Install: applications.commands

  • Guild Install: applications.commands, bot

Copy and paste the values into the Backoffice under the Discord connector configuration (appmixer:discord):

• clientId → "Client ID" from Discord

• clientSecret → “Client Secret” from Discord

• botToken → “Bot Token”

After saving, return to your flow in Appmixer. Click “Connect account” for the Discord connector, complete the authorization, and you’re ready to use Discord components in your flows.

Overview

The Join Component is used to merge multiple input connections. It forwards every received message to the output port without modification.

Usage

Input Ports

Output Ports

1. Connect Multiple Inputs

   • Attach multiple input sources to the in port.

2. Forward Messages

   • Every received message is immediately sent to the out

• Does Not Modify Messages: Messages are forwarded exactly as received.

• Useful for Routing: Can be used to merge multiple data streams into one processing path.

Overview

The CSV2JSON component converts a CSV file into a JSON file.

Input Parameters

Output Parameters

1. Provide File ID:

   • Select or upload the CSV file to be converted.

2. Processing:

   • The component processes the CSV file and converts it into JSON format.

XLSX2HTML Component

Overview

The XLSX2HTML component converts an XLSX (Excel 2007+ XML) file into an HTML table format.

Input Parameters

Output Parameters

1. Select the XLSX File

   • Choose an existing XLSX file by providing its fileId.

2. Processing

   • The component will convert the XLSX file into an HTML table.

Overview

The CSV2HTML component converts a CSV file into an HTML table. This allows for easier visualization and sharing of structured data.

Input Parameters

Output Parameters

1. Select the CSV File:

   • Provide the fileId of the CSV file to be converted.

2. Processing:

   • The component will transform the CSV file into an HTML table.

Overview

The HTML2XLSX component converts an HTML table file into an XLSX (Excel 2007+ XML Format) file.

Input Parameters

Output Parameters

1. Provide the File ID:

   • Select or upload an HTML file containing a table.

2. Conversion Process:

   • The component extracts tabular data from the HTML file and converts it into an Excel spreadsheet.

XLSX2CSV Component

Overview

The XLSX2CSV component converts an XLSX Excel 2007+ XML format file into a CSV file.

Input Parameters

Output Parameters

1. Provide File ID:

   • Select an XLSX file using its fileId.

2. Conversion Process:

   • The component processes the XLSX file and converts it into CSV format.

This component is useful for extracting tabular data from Excel files into a widely used CSV format for further processing.

Overview

The JSON2HTML component converts a JSON file into an HTML table.

Input Parameters

Output Parameters

1. Provide the JSON File:

   • Select or upload a JSON file using its fileId.

2. Processing:

   • The component reads the JSON file and converts it into an HTML table.

JSON2XLSX Component

Overview

The JSON2XLSX component converts a JSON file into an XLSX (Excel 2007+ XML Format) file.

Input Parameters

Output Parameters

Instructions

1. Select the Input JSON File:

   • Upload or provide the fileId of the JSON file to be converted.

2. Processing:

   • The component converts the JSON file into an XLSX format.

Overview

The AddRows component allows adding multiple rows to an existing dataset.

Input Parameters

Output Parameters

Instructions

1. Provide the Dataset:

   • Ensure the dataset is passed in the correct array format.

2. Add Rows Data:

   • Provide multiple rows in an array where each object represents a row.

Overview

The AddRow component allows adding a single row to a dataset.

Input Parameters

Output Parameters

Instructions

1. Provide the Dataset:

   • Ensure the dataset is passed in the correct array format.

2. Add Row Data:

   • Provide the new row as an object where keys match column names.

Overview

The AddColumn component allows adding a new column to an existing dataset.

Input Parameters

Output Parameters

Instructions

1. Provide the Dataset:

   • Ensure the dataset is passed in the correct array format.

2. Specify Column Details:

   • Enter the column name.

• Create a Calendly Developer account:

• Go to and sign up.

⚠️ Note: This is not your Calendly user account. It’s a separate developer account.

1. Create a new OAuth application:

You can find all the necessary information on how to register an OAuth app in Jira in their .

Access and create a new app. Click Create and select OAuth 2.0 integration.

Click on the "Register an app" button.

When you create an OAuth 2.0 (3LO) app, it's private by default. This means that only you can install and use it. If you want to distribute your app to other users, you must enable sharing.

Please follow the instructions in the to set up distribution.

You need to specify the scopes that your app will use. The Jira connector uses classic scopes for issue and instance operations, and granular scopes for project operations.

Note: The granular project scopes below apply to Jira connector version 4.0 and newer. Older connector versions use the classic manage:jira-configuration scope for project operations instead.

The Appmixer Fathom connector uses API key authentication. You do not need to register an OAuth app. Each user creates a personal API key in their Fathom account and enters it when they connect Fathom in Appmixer.

1. Log in to .

2. Open Settings (top right) and go to the API Access section of your user settings. The direct link is .

3. Click Add

First, you need to set a Quickbooks key and endpoint through the Backoffice in order to provide the Quickbooks components to your customers.

Go to the to create a new app.

Select the name and scope:

Then you receive your clientID and clientSecret.

Intuit issues two separate key pairs: Development keys work only with sandbox companies and Production keys work only with production companies. Configure the pair that matches the companies your users will connect.

Also add the redirect URL. Example: https://api.YOUR_SUBDOMAIN.appmixer.cloud/auth/quickbooks/callback.

Go the Appmixer BackOffice -> Configuration. Add new configuration: appmixer:quickbooks

The Condition Component evaluates expressions and directs data to either the true or false output port based on the result. It supports logical conditions using multiple operators and can process complex logical groupings.

The Switch component allows conditional branching of messages based on predefined expressions. It evaluates up to five conditions (out1 to out5) and routes messages accordingly. If none of the conditions match, the message is sent to the else output.

Go to GitHub → Settings → Developer settings → OAuth Apps → New OAuth App (for an organization-owned app: Organization settings → Developer settings → OAuth Apps).

• Application name and Homepage URL: anything your users should recognise.

• Authorization callback URL: https://<your-appmixer-api>/auth/github/callback — replace the host with your Appmixer API URL and keep the suffix /auth/github/callback.

Generate a client secret and create the appmixer:github

The Archive component allows you to create a ZIP or TAR archive from a set of files. You can also append files to an existing archive, provided it matches the specified format.

The Appmixer TypeSafe AI connector uses API key authentication. No OAuth app registration is required — you only need an API key from the TypeSafe console.

TypeSafe's Jev model does not generate text. You send it content together with typed questions (pick one of these options, rate on this scale, is this statement true) and it returns a decision limited to the options you supplied, with probabilities and a confidence score.

1. Open the and sign in with Google or with a code sent to your e-mail.

2. In the left sidebar, go to API Keys ().

Visit the tutorial for more information.

The On App Event Component triggers when an event is received from an external application, allowing automation workflows to respond dynamically to incoming app events.

This component listens for app events and processes incoming data, making it ideal for integrating external systems and event-driven workflows.

The LinkedIn Pages connector (appmixer:linkedinPages) publishes posts on behalf of LinkedIn company pages. It needs its own LinkedIn app with the Community Management API product.

Don't reuse the app you created for the LinkedIn connector (appmixer:linkedin). LinkedIn grants the Community Management API only to an app that has no other products, and the LinkedIn connector needs Sign In with LinkedIn using OpenID Connect.

Before you start

• A business email address. Personal addresses are rejected, and LinkedIn sends a verification email to the address you enter.

• Your organization's legal name, registered address, website and privacy policy URL.

• A LinkedIn Page of your organization, and a super admin of that page who will verify the app.

• An app name and logo that don't contain "LinkedIn", "Linked" or "In", or the LinkedIn or Microsoft logos.

1. Go to and create a new app.

   • Fill in the app name.

   • For LinkedIn Page, choose your organization's page.

   • Add the privacy policy URL and the app logo, then accept the legal agreement.

Create the appmixer:linkedinPages configuration in the and set clientId and clientSecret.

The connector requests the following scopes:

• r_basicprofile: the name of the connected member, which becomes the account name. This app gets no access to the member's email address.

• w_organization_social: publishing posts as a company page (CreatePost).

• rw_organization_admin: listing the pages the member manages, which fills the organization dropdown in CreatePost.

The connected member must be an administrator or content administrator of the page they post to.

• Development tier is what the app gets after the first approval. It allows 500 API calls per app and 100 API calls per member per 24 hours; the limits reset at midnight UTC. This is enough to build and test, not for production traffic.

• Standard tier removes these limits. Request it in the Products tab within 12 months of getting Development tier access, otherwise LinkedIn removes the access.

  • Be ready to describe your company, product and use case, and to give LinkedIn's reviewers test credentials.

• The authorization fails with an invalid or unauthorized scope error. The Community Management API isn't approved for the app yet, or one of the scopes above is missing on the Auth tab.

• Posting fails with 403 Forbidden. The connected member isn't an administrator or content administrator of the page. The error message includes LinkedIn's reason.

More in LinkedIn's documentation: , .

Overview

The AWS SNS Connector allows you to send SMS messages using Amazon Simple Notification Service (SNS). However, there are certain limitations and prerequisites that must be met for successful message delivery.

Prerequisites

Before using the AWS SNS Connector to send SMS messages, ensure the following:

1. SNS Sandbox Registration:

   • If your AWS account is in SNS SMS Sandbox Mode, SMS messages can only be sent to verified phone numbers added in the AWS Console.

   • To register a phone number, follow .

2. Region Compatibility:

   • The SNS SMS service may be region-dependent. Ensure the selected region supports SNS SMS services.

   • Messages might only be delivered if the selected region matches your AWS account’s region.

3. Spending Limit:

   • AWS imposes a default spending limit of $1 USD for SMS.

   • If the limit is reached, no SMS will be sent.

   • Check and increase the limit in the AWS SNS console under SMS settings.

4. IAM Permissions:

   • To enable SMS delivery logs, you must have the necessary IAM permissions.

   • Without proper permissions, viewing SMS failures or debugging will not be possible.

   • Check IAM policies and request permissions if needed.

• When an SMS is published via SNS, a 200 OK response is returned.

• However, this only confirms that SNS received the request. It does not confirm message delivery.

• To track the status of an SMS:

  • Enable CloudWatch Logs for SNS SMS (requires permissions).

1. Verify Phone Number:

   • Check if the recipient's number is added in the AWS SNS SMS sandbox.

2. Check Spend Limit:

   • Go to AWS SNS Console → Text Messaging (SMS) → Spend Limit