It looks like you’ve hit two distinct walls: the GraphQL syntax for customFields (the "Subselection required" error) and the challenge of listing Goals without hardcoding ARI/UUIDs.
Correct Syntax for customFields in goals_byIds
The error Subselection required for type 'TownsquareCustomField' of field 'node' means that node is an object, not a scalar. In GraphQL, when a field returns an object, you must explicitly define which sub-fields you want.
The Fix
You need to specify the fields inside the node. Since customFields often use interfaces or unions, you should use inline fragments (... on TypeName) to access the specific values.
GraphQL
query GoalQuery2 {
goals_byIds(
goalIds: "ari:cloud:townsquare:xxxxxx:goal/55541a4f-7a34-4d10-9170-154ea141cf2b"
) @optIn(to: "Townsquare") {
name
status {
value
}
progress {
percentage
type
}
customFields {
edges {
node {
id
name
key
__typename # Useful to identify the specific type
# Use fragments to get the value based on the field type
... on TownsquareTextCustomField {
value
}
... on TownsquareNumberCustomField {
value
}
... on TownsquareSelectCustomField {
option {
id
value
}
}
}
}
}
}
}
Key Points:
edges { node { ... } } always requires sub-fields inside the node.
If you aren't sure which types exist yet, query only the metadata (id, name, key, __typename) first. The __typename will tell you exactly which fragment to use.
2. How to Find Goals Without the ARI/UUID
You don't have to use goals_byIds exclusively. You can use search or listing queries to find the IDs dynamically.
2.1. Listing Goals by Workspace or Filter
Use goals_search to list goals and retrieve their ARIs:
GraphQL
query ListGoals {
goals_search(
query: {
# Optional filters
# text: "client"
# status: [PENDING, IN_PROGRESS]
}
first: 50
) @optIn(to: "Townsquare") {
edges {
node {
id # This is the ARI you need for updates
key # Human-readable key/slug
name
status {
value
}
}
}
}
}
2.2. Filtering by Text (Goal Name)
If you only have the name of the goal from a spreadsheet, search for it:
GraphQL
query SearchGoalsByName {
goals_search(
query: {
text: "Increase New Customers"
}
first: 10
) @optIn(to: "Townsquare") {
edges {
node {
id
name
}
}
}
}
3. Linking to Google Sheets Automation
Suggested Workflow:
Preparation: Your Google Sheet should have a column for the Goal Name (or internal Key) and a column for the Metric Value.
Resolution: Your script (Apps Script) calls goals_search to map the "Goal Name" from the sheet to the "Goal ARI (ID)" from the API.
Identification: Fetch the customFields for that ID to find which fieldId matches the metric you want to update.
Execution: Run a mutation (e.g., goalMetric_update or customField_update) passing the Goal ARI, the Custom Field ID, and the Value from the spreadsheet.
Tente implementar essas alterações e me avise se surgirem outros erros.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.