CONNECT APP
Build with Crowdin
Developer Tools
- OAuth
MCP
Give your agent Crowdin tools
Every Crowdin action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Crowdin account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "crowdin",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Add File to Project:
const result = await mcp.callTool({
name: "crowdin-add-file",
arguments: {
projectId: "Project ID",
file: "File Path Or Url",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "crowdin",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Add File to Project:
result = await session.call_tool("crowdin-add-file", {
"projectId": "Project ID",
"file": "File Path Or Url",
})API PROXY
Call the Crowdin API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Crowdin API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.example.com/v1/me",
})
// Any allowed Crowdin endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.example.com/v1/me
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkuZXhhbXBsZS5jb20vdjEvbWU?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Crowdin actions from your backend
Connect a user's Crowdin account once, then run Add File to Project on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "crowdin-add-file",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
crowdin: { authProvisionId: "apn_xxxxxxx" },
projectId: "Project ID",
file: "File Path Or Url",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="crowdin-add-file",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"crowdin": {"authProvisionId": "apn_xxxxxxx"},
"projectId": "Project ID",
"file": "File Path Or Url",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "crowdin-add-file",
"configured_props": {
"crowdin": { "authProvisionId": "apn_xxxxxxx" },
"projectId": "Project ID",
"file": "File Path Or Url"
}
}'TOOLS
Crowdin actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Add File to Project
actionAdds a file into the created project. See the documentationWritev1.0.3 -
Create Project
actionCreates a new project within Crowdin. See the documentationWritev0.0.2 -
List Machine Translation ID Options
actionRetrieves available options for the Machine Translation ID field.Read-onlyv0.0.1 -
List Project ID Options
actionRetrieves available options for the Project ID field.Read-onlyv0.0.1 -
List Source Language ID Options
actionRetrieves available options for the Source Language ID field.Read-onlyv0.0.1 -
List Storage ID Options
actionRetrieves available options for the Storage ID field.Read-onlyv0.0.1 -
Translate via Machine Translation
actionPerforms machine translation of the uploaded files. See the documentationWritev0.0.2
EVENTS
Crowdin triggers
Event sources your backend can deploy for users and receive through a webhook.
-
New Comment or Issue Added (Instant)
triggerEmit new event when a user adds a comment or an issue in Crowdin.Instantv0.0.1 -
New Directory Created
triggerEmit new event when a new directory is created.v0.0.1 -
New File Approved (Instant)
triggerEmit new event when a file is fully translated and approved.Instantv0.0.1
- App slug
- crowdin
- Authentication
- OAuth
- Categories
- Developer Tools
- Actions
- 7
- Triggers
- 3
- API proxy
- Available
OAuth scopes
These are the scopes Pipedream's managed Crowdin OAuth client requests when one of your users connects an account. Supply your own OAuth client to request a different set.
- notification
- project
- mt
- webhook
- ai