Hubspot automations

[gaspergrom]

Changes proposed ✍️

What

🤖 Generated by Copilot at 4826a24

This pull request adds a new HubSpot integration feature, which allows creating automations that send members or organizations to HubSpot based on certain conditions. It also improves the UI and code quality of the existing automation components, such as the automation form, list, and executions. It refactors the automation types configuration module and the name column of the automation list table to use a dynamic approach. It also updates some labels and URLs for the Slack and Discourse integrations.
​

🤖 Generated by Copilot at 4826a24

Sing, O Muse, of the skillful developers who wrought
Many wondrous automations for their loyal clients,
With the help of HubSpot, the mighty cloud-born god,
Who grants them power to sync and send their data.

Why

How

🤖 Generated by Copilot at 4826a24

• Add HubSpot integration feature that allows sending members or organizations to HubSpot based on certain conditions (link, link, link, link, link, link, link, link)
• Update automation types configuration to use a shared object and interface that supports new types of automations (link, link)
• Update automation form component to render the header, action, and button slots dynamically based on the type data object (link, link, link, link, link, link)
• Update automation list and executions components to display the name and icon of the automation type dynamically based on the automation types object (link, link, link, link, link, link)
• Update slack integration URL from /slack/ to /config/ to avoid conflicts with other integrations (link, link)
• Add new options for the automation trigger: member attributes match and organization attributes match (link)
• Update label of the button that verifies the webhook configuration from "Verify webhook" to "Verify config" (link)
• Add shared trigger component that handles the new activity and new member triggers (link)
• Move filter options components for new activity and new member triggers to a shared folder (link, link)
• Update logic for setting and displaying the automation name (link, link)
• Add v-if directive to the template element to avoid rendering unnecessary elements and prevent errors (link)

Checklist ✅

• Label appropriately with Feature, Improvement, or Bug.
• Add screehshots to the PR description for relevant FE changes
• New backend functionality has been unit-tested.
• API documentation has been updated (if necessary) (see docs on API documentation).
• Quality standards are met.

[themarolt]

member identities can now also have sourceId if it's needed

[epipav]

I updated processData so that sourceId is also inserted into the identity - However, I didn't change this logic because we also have this for organizations (and we don't have identities for organizations yet). I think it'll be less confusing if we get the sourceIds from syncRemote tables for both entities when pushing data