Skip to main content
Feedback

Kintone (Tech Preview) connection

The Kintone (Tech Preview) connection represents an authorized connection from an external application to the Kintone platform. The connection is authenticated by a private application; users can self-authorize to access their account information.

To learn more about users, administrators and permissions, refer to the Managing Permissions section in the Kintone Help docs.

If you have multiple accounts, use a separate connection for each and configure the URL accordingly. Pair a single connection with different Kintone operations to perform a unique action against a Kintone account.

Using the Connection tab

  1. Enter your Kintone subdomain in the Subdomain field. This is your “mycompany” from the mycompany.kintone.com. This is required for all authentication types.

  2. By default, Domain field is selected as kintone.com. For Japan region, use .cybozu.com.

  3. Select the authentication method for Kintone connection in the Authentication Type dropdown. Available options are API Token, Basic Authentication, OAuth 2.0.

  4. If the selected authentication type is:

    a. API Token

    • Click the Click to Set button.
    • Enter the API Token name and click Apply.
    • Enter the Kintone app ID in the App ID field. This is required when using API Token authentication.

    b. Basic Authentication

    • Enter the username for basic authentication.
    • Click the Click to Set button.
    • Enter the password and click Apply.

    c. OAuth 2.0

    • Enter the relevant details in the OAuth 2.0 tab.

  5. Connection Timeout is the number of seconds that the connector waits to complete the connection handshake until it times out. By default, it is set to 30 seconds.

  6. Read Timeout is the number of seconds that the connector waits to complete the FTP data transfer until it times out. By default, it is set to 60 seconds.

Using the OAuth 2.0 tab

note

  • For OAuth 2.0 authentication, you may need to specify the Boomi callback or redirect URL in the external application. The callback URL is https://platform.boomi.com/account/<your_account_ID>/oauth2/callback, where <your_account_ID> is your Integration account ID. You can also find your account ID in the Integration platform at Settings > Account > Account Information.

  • When you authenticate using OAuth 2.0 (Using service principal), you provide the service principal's credentials. Service principals are applications with a set of permissions registered in a tenant. You use these to obtain OAuth 2.0 tokens and communicate with the Kintone application. OAuth 2.0 authentication works for all supported operations with QUERY RECORDS, CREATE RECORDS, UPDATE RECORDS, DELETE RECORDS, FILE UPLOAD, and FILE DOWNLOAD.

  • Service principal tokens expire one hour after being issued. After that, the connector automatically renews and refreshes the token to ensure the operation runs successfully.

  1. In the Grant Type field, select the authorization code for administration tasks specific to a client. This refers to the way an application gets an OAuth 2.0 access token for client authentication to protected cloud resources. The connection provides Client Credentials to retrieve an access token directly instead of asking for user authorization.

  2. Enter the client ID in the Client ID field. This ID is associated with the service principal, which you can obtain when registering as a client with Kintone. You can use this unique ID to request authorized access to client data.

  3. In the Client Secret field, enter the client secret associated with the service principal, which you can obtain when registering with Kintone.

    • Click the Click to Set button to open the Password window. Enter or paste the alphanumeric client secret associated with the Client ID.
    • Click Apply when you are done. Enable pop-up windows in your browser.

  4. Enter the authorization token URL, provided by the authorization server, in the Authorization Token URL field.

  5. In the Scope field, enter the scope, which is the URL list of the permissions (case-sensitive and separated by a space), defining the extent and access range to protected cloud resources. If you change scope permissions, you need to reauthenticate to ensure that it grants all of the requested permissions.

  6. In the Access Token URL field, enter the URL of the token endpoint, specific to each user, that the Kintone account instance uses to retrieve and refresh tokens.

Test connection

You can test your connection settings before you use or save the connection in a process. The Test Connection ensures that your specified settings are correct, valid, and accessible. If the test connection is successful, you can save the connection. Otherwise, review and correct any incorrect settings, then test again.

note

You can only run the Test Connection to validate the connection with Kintone.

On this Page