Integrations

Open Dashboard → Integrations and select the Claron project

You need permission to manage that project's integration.

Choose an available provider and Connect

Authorize an external account with access to the intended team/project/channel, or enter the provider credential/webhook requested by its form.

Choose the destination and default status/field mapping, then save the configuration

A successful authorization alone does not choose a ticket destination.

Use Test to check the connection

Then push a controlled annotation and inspect the resulting ticket or notification in the provider. A passing connection test alone does not prove delivery or sync.

For any offered sync option, enable it deliberately and test one change in each required direction

Verify comments and attachments separately; do not assume every provider mirrors every field.

Authorize the intended workspace

Choose Linear → Connect for the selected Claron project. Use a Linear account with access to the team that should receive reports.

Choose the team and default state

In the configuration panel, select team, then default state, and save. States belong to the selected team; select a new state if you change teams.

Check the issue and status workflow

Test the connection, push a sample annotation, and open its linked Linear issue. Confirm the team, title, and state. Test a supported status change back in Claron before relying on two-way updates.

Authorize Jira access

Choose Jira → Connect and authorize the intended Atlassian account. It needs access to the Jira project and permission to create its issues.

Select the ticket destination

Select project, issue type, and default status in that order, then save. Check that the displayed projects belong to the Jira site you intended to authorize.

Check a created issue

Test the connection, push a sample annotation, and open the Jira issue. Confirm project, issue type, priority, and description. If Jira rejects it, check required fields and the project's available priorities; successful sign-in alone does not satisfy those requirements.

Authorize board access

Choose Trello → Connect using an account that can add cards to the intended board.

Choose board and list

Select board, then list, and save. A list from a previous board is not the destination for the newly selected board.

Verify the card

Test the connection and push a sample annotation. Open the created card and check that it is in the chosen board and list, with the expected report link.

Authorize project access

Choose Asana → Connect with an account permitted to add tasks to the intended project.

Choose the task destination

Select workspace, project, and default section, then save. If a project is missing, check the authorized account's membership before reconnecting.

Verify the task

Test the connection, push a sample annotation, and inspect the Asana task's project, section, title, and report link.

Authorize workspace access

Choose ClickUp → Connect with access to the workspace and list that should receive reports.

Choose the list and status

Select workspace, space, list, and default status, then save. Recheck the downstream selections whenever you change their parent destination.

Verify the task

Test the connection and push a sample annotation. Inspect the ClickUp task's list, status, priority, and report link rather than treating authorization as proof of correct mapping.

Provide the requested credential

Choose Shortcut → Connect and use the credential requested by the form, from an account that can create stories in the intended workspace.

Choose team and workflow state

Select team and workflow state, then save. Check that the state is appropriate for the stories you are creating.

Verify the story

Test the connection, push a sample annotation, and inspect the story's team, workflow state, and report link. Resolve webhook-registration warnings before expecting incoming updates.

Grant database access

Choose Notion → Connect and authorize or provide the credential requested by the form. Share the intended database with that connection.

Choose the database

Select database and save. If it is missing, check its sharing permissions for the connection; your own ability to open it is not sufficient.

Verify the page

Test the connection and push a sample annotation. Inspect the new page in the selected database and its title, report link, and available properties.

Authorize board access

Choose Monday → Connect and provide the authorization or credential requested by the form. Use an account allowed to create items on the intended board.

Choose board and status mapping

Select board, status column, and default status, then save. The selected status must belong to that board's chosen column.

Verify the item

Test the connection and push a sample annotation. Check the created item's board, mapped status column, title, and report link.

Authorize the workspace

Choose Slack → Connect and approve access in the intended Slack workspace. Workspace app-installation rules can require an administrator's approval.

Choose the channel

Select channel in Claron's configuration panel and save. Ensure the connection can post there; do not assume a channel in another workspace is available.

Verify a notification

Test the connection, then trigger an enabled annotation event and inspect the message in that channel. Check project notification preferences if authentication succeeds but no event message arrives.

Create a channel webhook

In Discord, use a channel you are allowed to manage and create its webhook. Copy the webhook URL privately; anyone with that credential may be able to post to the channel.

Connect the webhook

Choose Discord → Connect for the intended Claron project and enter the webhook URL requested by the form. The webhook itself selects the channel; there is no separate channel picker.

Verify delivery

Test the connection, trigger an enabled annotation event, and inspect the message in Discord. If the webhook is deleted or rotated, update the saved connection and test again.