No, it’s not a requirement for the dbt project or the profile to be named “normalize”. The name of your dbt project is defined in the dbt_project.yml file and can be any valid name that reflects your organization’s name or the intended use of the models (source). The profile name is also configurable and should match the profile name specified in your dbt_project.yml file. If you change the profile name in both dbt_project.yml and profiles.yml, it should work fine with Airbyte (source). However, if you prefer to use your own profiles.yml stored in the git repository or in the Docker image, you can specify an override with --profiles-dir=<path-to-my-profiles-yml> in the dbt CLI arguments (source). Remember, if you specify a custom profile file, you are responsible for securely managing the credentials. Currently, Airbyte doesn’t have a way to manage and pass secrets and it’s recommended you let Airbyte pass this to dbt (source).