Summary
The user is facing an issue where the transformation is not running after the sync job between DBT Cloud and Airbyte Cloud. The logs show a 401 error with an ‘Invalid token’ message when invoking the webhook operation for DBT Cloud.
Question
Hello Airbyte Community,
I am trying to integrate DBT Cloud with Airbyte Cloud. I’ve configured the connection using the access URL in the format https://<ACCOUNT PREFIX>.<http://us1.dbt.com/|us1.dbt.com/>
and a service token. The connection appears to be working since I can select DBT Cloud jobs within Airbyte.
However, the transformation is not running after the sync job. When I check the logs, I see the following:
2024-08-21 09:21:33 platform >
2024-08-21 09:21:33 platform > Invoking webhook operation XXXXXXXXXXXXXXXX...
2024-08-21 09:21:34 platform > Invoking webhook operation "dbt cloud" using URL "<https://cloud.getdbt.com/api/v2/accounts/XXXXXXXXX/jobs/XXXXXXXXX/run/>"...
2024-08-21 09:21:35 platform > Webhook operation "dbt cloud" (XXXXXXXXXXXXXXXX) response: 401 {"status": {"code": 401, "is_success": false, "user_message": "Invalid token.", "developer_message": null}, "data": null}
2024-08-21 09:21:35 platform > Webhook XXXXXXXXXXX completed unsuccessfully
2024-08-21 09:21:35 platform >
2024-08-21 09:21:35 platform > ----- END POST REPLICATION OPERATIONS -----```
Interestingly, when I use Postman to make an API call to `https://<ACCOUNT PREFIX>.<http://us1.dbt.com/api/v2/accounts/XXXXXXXXX/jobs/XXXXXXXXX/run/|us1.dbt.com/api/v2/accounts/XXXXXXXXX/jobs/XXXXXXXXX/run/>`, it works fine.
Could someone help me figure out why the transformation isn't running as expected in Airbyte?
Thank you!
<br>
---
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1724233785702249) if you want
to access the original thread.
[Join the conversation on Slack](https://slack.airbyte.com)
<sub>
["dbt-cloud", "airbyte-cloud", "transformation", "webhook", "401-error", "invalid-token"]
</sub>