-
Notifications
You must be signed in to change notification settings - Fork 1
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
[Feature Request]: Tag for gtfs-contact in hubspot for every agency #575
Comments
@vevetron Hubspot has "association labels" that should be able to work for this use case. The CS team can discuss this further and get back to you! |
All contacts on the Reports Site distribution list now have the @AnthonyRollins I believe because the association label was set as a |
I'm trying to figure out how to pull this using python and the hubspot api. |
@laneymangan I don't think we need to use the association labels here as we already have a @vevetron We need to mark all contacts that are GTFS Contacts as |
@AnthonyRollins @laneymangan I read over this and wanted to share that we do have a Either way, it seems like we would have to do some additional work to ensure Vivek can pull an accurate list, however he does so: I can honestly say I have no idea if there is a benefit to doing this as a formal association versus just making use of the existing custom property, so I don't really have an opinion either way, but I think this is where we stand. |
I'm cool with the existing roles in Hubspot and made this map to the kind of contacts we want to collect at transit agencies with the help of Caltrans District Staff:
|
Feature Request
In the future we might automate sending emails that your gtfs is expiring. To do that we need to know who to send it to in an automated fashion. Thus it'd be valuable if there was a tag on people at agencies that defined them as a good contact person.
Perhaps CS can develop that tag and over time as they work with agencies, can start tagging contacts accordingly.
Is this request related to a problem?
There isn't a problem yet. But maybe we can move towards reducing the time CS spends on these minor issues that could just be an automated email rather than needing a human touch.
Use Case
e.g.
Additional Info
None
The text was updated successfully, but these errors were encountered: