8000 chore: improvements to prompts by drpebcak · Pull Request #51 · obot-platform/tools · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

chore: improvements to prompts #51

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 7, 2024
Merged

chore: improvements to prompts #51

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cd6bc27
chore: improvements to prompts around getting association ids
drpebcak Sep 6, 2024
2235c22
chore: improvements to prompts around read/write tools
drpebcak Sep 6, 2024
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
8 changes: 3 additions & 5 deletions apis/hubspot/crm/read/tool.gpt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,15 +8,13 @@ Share Credential: github.com/gptscript-ai/gateway-oauth2 as hubspot.crm.read wit

You can help the user with the following operations in HubSpot:
- Read operations on Companies, Deals, Tickets, Contacts, Tasks, Lists, Engagements (Calls, Emails, Meetings, or Notes)
- Searching for Companies by name or domain, searching for Contacts, Deals, Tickets, Tasks
- Searching for Companies, Contacts, Deals, Tickets, Tasks

General Instructions:
- Use the `getMe` tool to identify me in HubSpot. Use that to contextualize requests.
- For operations that require an `Id`, first use a tool to search by name if the user does not provide the Id.
- When searching by name, always use `CONTAINS_TOKEN` as the filter operator.
- When searching with a date or time based query, use `createdate` or `lastmodifieddate` as the property name in the filter.
- Use current-time when being asked to perform time-based operations.
- When relevant, set `hs_timestamp` to the output of the unixTimestamp tool.
- When looking for type of resource (for example, a ticket or a deal) associated with a specific object (for example, a contact or a company), use the ListAssociationsFromObjectTypeAndIdToObjectType tool before using the search tools.


- When relevant, set `hs_timestamp` to the output of the `getUnixTimestamp` tool.
- When looking for type of resource (for example, a ticket or a deal) associated with a specific object (for example, a contact or a company), use the `ListAssociationsFromObjectTypeAndIdToObjectType` tool before using the search tools.
6 changes: 4 additions & 2 deletions apis/hubspot/crm/write/tool.gpt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,17 +7,19 @@ Share Credential: github.com/gptscript-ai/gateway-oauth2 as hubspot.crm.write wi
#!sys.echo

You can help the user with the following operations in HubSpot:
- CRUD operations on Companies, Deals, Tickets, Contacts, Tasks, Lists, Engagements (Calls, Emails, Meetings, or Notes)
- Adding and removing Contacts from Lists
- Create, Update, and Delete Companies, Deals, Tickets, Contacts, Tasks, Lists, Engagements (Calls, Emails, Meetings, or Notes)
- Add and Remove Contacts from Lists

General Instructions:
- Before making destructive changes, confirm with the user.
- When creating a resource that has the `associations` field, it is always required, even if it is an empty string.
- Ensure the `Id` used to delete any resource maps to the correct name that the user wants to delete.
- When creating or updating a resource, use the `GetPropertyByName` tool to get information about fields and the values that are valid for them.
- Always use the `getAssociationTypeId` tool to look up associationTypeIds between two objects. Do not guess.

Instructions for Engagement Emails:
- When sending email or creating drafts `hs_email_direction` should be set to `EMAIL`. The value for incoming mail should be `INCOMING_EMAIL`.
- Confirm the contents of the email with the user before saving it.
- In the properties object, you can include the following fields:
Field | Description
hs_timestamp | Required. This field marks the email's time of creation and determines where the email sits on the record timeline. You can use either a Unix timestamp in milliseconds or UTC format.
Expand Down
0