Renaming fields with aliases in Connectors - The Weekly Wisdom - Edition #12

:graduation_cap: Welcome to The Weekly Wisdom

:spiral_calendar: Edition #12 - 24 Jul 2025
:label: Topic tags - Connectors odyssey
:bell: Stay in the loop: Subscribe to the “The Weekly Wisdom” category to get notified when new posts drop—no FOMO here.


Hey all! :waving_hand: @Michelle_Mabuyo here from the Apollo Education team. I’m a Developer Educator and I build courses for Odyssey, our official learning platform.

I’m back for the next edition of a multi-part series to teach you the basics of Apollo Connectors: a powerful way to bring existing REST APIs into your graph, all through configuration in the schema.

:light_bulb:This week’s learning: Renaming fields with aliases in Connectors

When your REST API returns a field like description but your schema expects tagline, you can map it like this


selection: """
tagline: description

"""

This works for nested fields too! For example, simplifying tagId to id to follow GraphQL schema naming conventions.

selection: """
tags: tags { 
     id: tagId
     name
}

Use this to keep your schema clean and client-friendly, without needing to change your backend.

:magnifying_glass_tilted_right: Want to go deeper?

Practice this hands-on in Lesson 3 of “Expressions in Connectors: Mapping and Transforms” on Odyssey.

Take the course


:speech_balloon: Share your thoughts in the thread below :down_arrow:

How often do you run into mismatched field names?