• on create: add webhook
• on destroy: delete webhook
• on run: handling webhook

The body of the webhook request is sent as application/x-www-form-urlencoded data.

Currently the fronend redirect url is localhost, we should derive it using system variable.

The webhook trigger is url is http (not https) also missing s (after webhook)

The Webhook Trigger should static link on the interface (Currently it's showing that there is dynamic link that will be generated), with the following format api_url/flows/FLOW_ID/webhook

Please add a note this link will only works for deployed collections.

We should allow multiple users to sign up in the backend.

For the following instance entity, we should support the following action.

1. List by project Id (Endpoint)
2. Get by Id (Endpoint)
3. Delete
4. Create / Update Instance (Endpoint).
   This action happens when user press Publish inside collection builder when the user want to run latest collection / flows.

This endpoint should update flow versions and collection version inside the instance entity, after we need to handle creation / destroy of triggers like schedule.

I suggest this service should emit events on create / update / delete of instance, and there would be a different listeners that handle triggers using pub sub pattern.

Listeners would the following

1. Schedule Trigger: create / destroy previous one
2. Component Trigger (Polling): Create Scheduling Job Every 15 minutes that's call run
3. Component Trigger (Webhook): This should call onEnable / onDisable

I suggest to use BullMQ to create repeatable jobs, Redis is installed.

Checkout Publisher / Subscriber Implementation in this comment.

Add the following
-> Link inside sign-up form to redirect to sign-in form.
-> Redirection to Sign-Up only if there is no users from sign-in.

Triggers:

• New Issue is created.

Property:

• Github OAuth2

Acceptance Criteria:

• Prefer Webhooks over Polling
• Sample Data is provided in the trigger.

In Mautic we implement an automated way to tag and release our versions, I can help you implement a similar process, I just need to have a conversation with @abuaboud about the releasing process

Files for reference
https://github.com/mautic/mautic/blob/5.x/.github/workflows/release.yml
https://github.com/mautic/mautic/blob/5.x/.github/workflows/generate-release-notes.yml

• Authentication: OAuth 2.0
• Endpoint: Add a member to list
• Required inputs:
  • list-id (dynamic list)
  • email (string)
  • status (string)

Check if any of the triggers in the first connectors will need polling, and implement polling if it's needed now. Otherwise, keep the issue for later.

I'm working with their team but we need to get the technical work done. Here is the guideline to get it done:
https://github.com/digitalocean/marketplace-partners

We should show an message on success, to visit localhost:8080 on the docker compose success.

We should add discord to our documentation, and how the user should create an application (client and secret) and obtain the bot token.

For the following instance run entity, we should support the following action.

1. List by project Id (Endpoint)
2. Get by Id (Endpoint)
3. Create / Update Run ( Service layer only)

The following required to complete sign-in / sign-up.

1. Allow addition of new JWT types
2. Schema Validation for the endpoints

Trigger:

• TaskCreated
• Task Updated
• Task Deleted
• Task Comment Posted
• Task Comment Updated

Property:

• Clickup OAuth2

Acceptance Criteria:

• Prefer Webhooks over Polling
• Sample Data is provided in the trigger.

After the first set up, we'll ask users to enter their emails to sign up for our newsletter for product updates and contribution opportunities.

Trigger on Google Calendar when new event or updated (except deleted) is created.

Property:

• Google OAuth2

Acceptance Criteria:

• Prefer Webhooks over Polling
• Sample Data is provided.

We need the following fixes to the backend to be able to have a demo instance:
1)Instead of sending back bad request when a token has expired or is invalid, please send back unauthorized.
2)Add a flag who's value is the text which will be shown as a warning in the front-end (WARNING_TEXT).
3)The user object returned in a sign up/sign in response, doesn't container (trackEvents) property, it should.
4)Sign up endpoint returns an internal server error when someone tries to sign up with an already existing email.

@ashrafsamhouri: please install this integration https://github.com/apps/stale, it will help track opened issues for long time and archive them if there is no activity, I will open a PR with the yaml file to support this bot

We'll ask for permission to track users behavior anonmyously to improve the product, and then send data to our PostHog server.

The Documentation should show how to create and test sample piece end to end

Create an Demo Instance

Creates an event on Google Calendar.

Properties (Minimum):
Google Oauth2

STR:

• Start a flow.
• Click "Replace Trigger" icon next to the trigger step.
• Click "+" beneath the trigger.
• Click "Replace Trigger" icon next to the trigger step.
• Click "+" beneath the trigger.
• Click "Replace Trigger" icon next to the trigger step.
• Click "+" beneath the trigger.

Watch how tabs will get created in the panel.

Video: https://www.loom.com/share/b4bdaf7243a340ad96f1748f44077087

Today as User I have no idea what app trigger payload looks like, for example "New Github Star".

I suggest we should add Sample Payload for each trigger and use it for testing and development.

The frontend should parse the components metadata endpoint and show the triggers in the interface with their configs.

With the new backend, a new way for handling the code piece emerged:

Before:
1)On adding a code step, we put a boiler plate artifact (package.json + index.js) in a zip file and upload it to a separated endpoint from the update flow endpoint.
2)On retrieval, we download a zip file containing the artifact, and unzip it and pass its content to the code controller.
3)On update, we upload a zip file to the server containing the artifact to a separated endpoint from the update flow endpoint.

Now:
1)On adding a code step, we put a boiler plate artifact in the settings of the the code step as a json object that is base64 encoded and send it to the server.
2)On retrieval, we download the artifact as a zip file containing both index.js and package.json, then we pass them to the code form control as a JSON object.
3)On update or execute, we upload the artifact as a base64 string after zipping the artifact JSON object.

The issue is in the frontend variables (environment.prod.ts) the api url is using localhost and when visiting from another device, frontend will try to call localhost instead of server ip.

Steps to Reproduce:

• Enter a Server (Not localhost)
• Follow installation instruction
• Go to IP:8080 and try to login

Components Like Slack, have an option to select channel, such dropdown need to be refreshed.

The frontend should call backend to fetch the new options.

Steps to Reproduce:

• Create New Collection
• Create New Flow
• Add Slack Action
• The channel list should be dynamic depends on authentication.

1)Add an (all) tab for the step list (all, core, apps) for both triggers and steps.
2)On empty trigger, make display name "Select Trigger" and don't open right side panel unless it is clicked.
3)Add link to connectors documentation at the top of the input form (https://activepieces.com/docs/pieces/apps/{{connectorName}})
4)Name the right side panel title as "Select Triggers/Select Steps" instead of just "Triggers/Steps".
5)Increase the add button size and make it look darker to look actionable.
6)Replace "replace trigger" icon, it looks like refresh.
7)Remove "Versions" from the dropdown next to the collection name.
8)If there are no authentications, in the shown dropdown insert an add button.
9)Add delete flow validation for the last flow in a collection.
10)Show correct browser tab title when the flow builder is entered and when a collection is renamed.

• on create:
  • update settings
  • create subscription
• on run: verify signature
• on destroy: delete subscription

useful info

• Webhook URL must be served over HTTPS (source)

When running the code action through the full code editor, It won't work.

Steps to Reproduce

• Create New Collection
• Create New Flow
• Add Code Action
• Open full code editor
• Click Test Code

1)After our team created a server to manage authentication of our own apps for connectors, now comes the need to add a toggle button in the dialog shown when a user clicks "new authentication", the job of the toggle button is to give the user the choice of either using the activepieces app credentials to get an access token, or use their own app credentials.

2)Use appName to filter the authentication dropdown for app steps.

The HTTP Library lacks the following

1. Send Request only returns the body (no status).
2. appending query params to the url ?limit=10 doesn't work, it has to be done through the queryparams

Note: We should update the documentation after doing any changes.

This task should provide templates and documentation for how to host activepieces on the following platforms