Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]: Formbricks self hosted API does not work #4668

Closed
mantis64 opened this issue May 11, 2024 · 3 comments · Fixed by #4676
Closed

[BUG]: Formbricks self hosted API does not work #4668

mantis64 opened this issue May 11, 2024 · 3 comments · Fixed by #4676
Labels
🤷‍♂️🤷‍♀️ untriaged Need attention from maintainer in activepieces

Comments

@mantis64
Copy link

Describe the bug
I am trying to use my self hosted activepieces work with my self hosted formbricks.

To Reproduce
Steps to reproduce the behavior:

  1. Go to ' flows and try and connect formbricks'
  2. I generate an API from my self hosted formbricks and insert into my activepieces'
    However there is a connection error and I am unable to connect formbricks and activepieces together.

Expected behavior
I would expect them to be able to connect. However presumably it is trying to connect to the actual formbricks and not my domain.

How can I make it work with my self hosted formbricks please?

@abuaboud abuaboud added the 🤷‍♂️🤷‍♀️ untriaged Need attention from maintainer in activepieces label May 12, 2024
@abuaboud
Copy link
Contributor

#4676

@abuaboud abuaboud linked a pull request May 13, 2024 that will close this issue
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If this issue is continuing with the latest stable version of Activepieces, please open a new issue that references this one.

@mantis64
Copy link
Author

Still does not work under the latest build

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🤷‍♂️🤷‍♀️ untriaged Need attention from maintainer in activepieces
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants