Skip to content

docs: split evals runbook into working and non-working sections #98

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Sep 26, 2025
Merged

docs: split evals runbook into working and non-working sections #98

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
74813b1
docs: split the evals runbook between working/non-working
aaronsteers Sep 25, 2025
71407da
Update connector_builder_agents/evals/README.md
aaronsteers Sep 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 15 additions & 2 deletions connector_builder_agents/evals/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,22 @@ Manual Runbook:

```bash
poe build-connector --api-name=Hubspot --existing-connector-name=source-hubspot --existing-config-name=config
poe build-connector --api-name="Sharepoint Lists" --existing-connector=source-microsoft-lists --existing-config-name=config
poe build-connector --api-name=Jira --existing-connector-name=source-jira --existing-config-name=config
poe build-connector --api-name=Sentry --existing-connector-name=source-sentry --existing-config-name=config
poe build-connector --api-name=Stripe --existing-connector-name=source-stripe --existing-config-name=config
```

Not yet tested to succeed:

```bash
# Sentry seems to maybe be working, but runs into timeout issues
# perhaps due to data volumes.
poe build-connector --api-name=Sentry --existing-connector-name=source-sentry --existing-config-name=config

# Complaints of the auth not having the necessary access.
# Could be an auth issue or just not using the OAuth/endpoints correctly.
poe build-connector --api-name="Sharepoint Lists" --existing-connector-name=source-microsoft-lists --existing-config-name=config --additional-instructions="Start with the 'lists' API endpoint to get a list of lists."

# Auth is notoriously a bit weird for Google. The integ auth is in JSON form (in an env var),
# but the API might want it more granular or as a file.
poe build-connector --api-name="Google Analytics v4" --existing-connector-name=source-google-analytics-v4 --existing-config-name=service_config
```
Loading