Connect Gitlab and TheTVDB
Describe what you want to happen between Gitlab and TheTVDB in plain words. HumDay writes the program, proves it on real data, and runs it — no node graph, no field mapping, and no connector to wait for.
What HumDay can do on each side
Read from each provider’s own published API description, in their words.
Gitlab
358 documented operations. See all Gitlab operations
- POSTAdd new email address to the currently authenticated user
/v3/user/emails - POSTCreate a user. Available only for admins
/v3/users - POSTAdd an email address to a specified user
/v3/users/{id}/emails - POSTCreate a new project issue
/v3/projects/{id}/issues - POSTAdd a new SSH key to the currently authenticated user
/v3/user/keys - POSTCreate new file in repository
/v3/projects/{id}/repository/files
TheTVDB
31 documented operations. See all TheTVDB operations
- PUTAdds the supplied series ID to the user’s favorite’s list
/user/favorites/{id} - DELETEDeletes the given series ID from the user’s favorite’s list
/user/favorites/{id} - DELETEThis route deletes a given rating of a given type
/user/ratings/{itemType}/{itemId} - POSTReturns a session token to be included in the rest of the requests
/login - PUTThis route updates a given rating of a given type
/user/ratings/{itemType}/{itemId}/{itemRating} - GETReturns a list of query params
/user/ratings/query/params
How a Gitlab and TheTVDB automation gets built
- Describe the outcome. Say what should happen — not which endpoints to call. HumDay works out which operations each side needs.
- Approve the contract. Before anything is built you see exactly what it will do in Gitlab and TheTVDB, and what it will never do.
- See it proven. The program runs and shows you the result before it is allowed near either live account.
- Grant access, then go live. You approve the specific operations it may use on each side — and only those.
Related integrations
- Gitlab and OData for namespace microsoft.graph11,770 operations
- OData for namespace microsoft.graph and TheTVDB11,443 operations
- Cloudflare and Gitlab3,480 operations
- Cloudflare and TheTVDB3,153 operations
- Gitlab and NetBox1,202 operations
- NetBox and TheTVDB875 operations
- GitHub and Gitlab1,169 operations
- GitHub and TheTVDB842 operations
- Gitlab and Mist1,126 operations
- Mist and TheTVDB799 operations
Questions about connecting Gitlab and TheTVDB
- Can Gitlab connect with TheTVDB?
- Yes. HumDay reads both providers' own published API descriptions and derives what each one can do, so neither side needs a hand-built connector before you can use it.
- How do I connect Gitlab to TheTVDB?
- Describe the outcome you want in plain words. HumDay agrees a contract with you saying exactly what it will do, writes the program, and shows you a proof run before either account is touched.
- Do I need to write code to integrate Gitlab and TheTVDB?
- No. There is no node graph to wire up and no field mapping to do. You say what should happen and HumDay works out which operations it needs from each side.
- What can HumDay do across Gitlab and TheTVDB?
- Gitlab publishes 358 documented operations and TheTVDB publishes 31. HumDay only ever uses the specific ones your approved contract needs.
- Is it safe to connect both accounts?
- Your credentials are stored encrypted and never appear in chat, code, or logs. Anything that writes to either Gitlab or TheTVDB is held behind an approval you grant explicitly.
Where this came from
Operations are read from the published API descriptions for Gitlab and TheTVDB. Descriptions are each provider’s own words, not ours.