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

[Components] domo #14900

Open
pipedream-component-development opened this issue Dec 10, 2024 · 5 comments · May be fixed by #15487
Open

[Components] domo #14900

pipedream-component-development opened this issue Dec 10, 2024 · 5 comments · May be fixed by #15487
Labels
triaged For maintainers: This issue has been triaged by a Pipedream employee

Comments

@pipedream-component-development
Copy link
Collaborator

pipedream-component-development commented Dec 10, 2024

domo

URLs

Polling Sources

new-dataset

Prompt

Emit new event when a new dataset is added to the Domo instance. Users can configure optional filters such as dataset owner or dataset tags to narrow the scope.

URLs

new-data-in-card

Prompt

Emit new event when data within a specific card is updated. Users must provide the card ID, and they can optionally specify thresholds or conditions for the data updates. projectId and listId have async options

URLs

new-alert-triggered

Prompt

Emit new event when an alert is triggered in Domo based on predefined rules. Users can configure filters for specific alert types or related datasets.

URLs

Actions

add-data-to-dataset

Prompt

Add new rows of data to an existing dataset in Domo. Users must provide the dataset ID and the data in the form of a JSON object or array.

URLs

update-card-description

Prompt

Update the description of an existing card in Domo. Users must provide the card ID and the new description text.

URLs

@vunguyenhung vunguyenhung added the triaged For maintainers: This issue has been triaged by a Pipedream employee label Dec 13, 2024
@luancazarine luancazarine self-assigned this Dec 16, 2024
@luancazarine luancazarine removed their assignment Dec 23, 2024
@luancazarine luancazarine self-assigned this Feb 3, 2025
@luancazarine luancazarine linked a pull request Feb 3, 2025 that will close this issue
@luancazarine luancazarine moved this from Doing to Blocked in Component (Source and Action) Backlog Feb 4, 2025
@luancazarine
Copy link
Collaborator

The Domo API is not working very well, several endpoints are returning 500 and some 403 when they shouldn't,
So as discussed with @sergio, I'm moving this to Blocked for now and then he will analyze it better.

@luancazarine luancazarine removed their assignment Feb 4, 2025
@sergio-eliot-rodriguez
Copy link
Collaborator

@luancazarine can you share a bit more details about the errors you are getting?
an example for each error number with the following format would be great:

couldn't test the create-ad-group component because I got the following error:

{
"api_error_code": "403",
"message": "Advertiser 578797488048178883 doesn't have any billable payment information associated with the account."
}

@luancazarine
Copy link
Collaborator

Hi @sergio-eliot-rodriguez, OF course I can.

For example, when I try to get users or cards, it work as expected

Image

Image

but if I want to get a specifc card, it doesn't work

Image

or when I try to update a card description following the API doc

Image
https://developer.domo.com/portal/ce5767e6694f4-update-chart-card-definition

@sergio-eliot-rodriguez
Copy link
Collaborator

Ok I reached out to support via email with these details. I will posting updates here

@sergio-eliot-rodriguez
Copy link
Collaborator

sergio-eliot-rodriguez commented Feb 18, 2025

Meet up with Domo requested by their support team. This should remain blocked per discussion on Slack here for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triaged For maintainers: This issue has been triaged by a Pipedream employee
Development

Successfully merging a pull request may close this issue.

4 participants