Sync Android drawable assets from Figma to GitHub via PR (multi-density PNG)

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Sync Android drawable assets from Figma to GitHub via PR (multi‑density PNG) This n8n workflow automatically fetches design assets (icons, buttons) from Figma, exports them into Android drawable fo...

Best for

File Management automation workflows
Multimodal AI automation workflows
intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.merge, n8n-nodes-base.httprequest, n8n-nodes-base.if, n8n-nodes-base.manualtrigger, n8n-nodes-base.code, n8n-nodes-base.stickynote

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by WeblineIndia.

Original n8n.io source

1.1 Workflow description

Title: Sync Android drawable assets from Figma to GitHub via PR (multi-density PNG)
Workflow name: Sync Android drawable assets from Figma to GitHub via PR (multi-density PNG)

Sync Android drawable assets from Figma to GitHub via PR (multi‑density PNG)

This n8n workflow automatically fetches design assets (icons, buttons) from Figma, exports them into Android drawable folder formats based on resolution (e.g., mdpi, hdpi, etc.) and commits them to a GitHub branch, creating a Pull Request with all updates.

Who’s it for

Android / Flutter developers managing multiple screen densities.
Design + Dev teams wanting to automate asset delivery from Figma to codebase.
Mobile teams tired of manually exporting assets, resizing, organizing and uploading to GitHub.

How it works

Execute Flow manually or via trigger.
Fetches all export URLs from a Figma file.
Filters out only relevant components (Icon, Button).
Prepares Android drawable folders for each density.
Merges components with folder mapping.
Calls Figma export API to get image URLs.
Filters out empty/invalid URLs.
Downloads all images as binary.
Merges images with metadata.
Renames and adjusts file names if needed.
Prevents duplicate PRs using conditional checks.
Commits files and opens a GitHub Pull Request.

How to set up

Set up your Figma token (with file access)
Get Figma File Key and desired parent node ID
Connect your GitHub account in n8n
Prepare a GitHub branch for uploading assets
Add your drawable folders config
Adjust file naming logic as per your code style
Run the workflow

Requirements

Tool	Purpose
Figma API Token	To fetch assets and export URLs
GitHub Token	To commit files and open PR
n8n	Workflow automation engine
Figma File Key	Target design file
Node Names	Named like `Icon`, `Button`

How to customize

Add more component types to extract (e.g., Avatar, Chip)
Change drawable folder structure for other platforms (iOS, Web)
Add image optimization before commit
Switch from branch PR to direct commit if preferred
Add CI triggers (e.g., Slack notifications or Jenkins trigger post-PR)

Add‑ons

Slack Notification Node
Commit summary to CHANGELOG.md
Image format conversion (e.g., SVG → PNG, PNG → WebP)
Auto-tag new versions based on new asset count

Use Case Examples

Auto-export design changes as Android-ready assets
Designers upload icons in Figma → Devs get PR with ready assets
Maintain pixel-perfect assets per density without manual effort
Integrate this into weekly design-dev sync workflows

Common Troubleshooting

Issue	Possible Cause	Solution
Export URL is `null`	Figma node has no export settings	Add export settings in Figma for all components
Images not appearing in PR	Merge or file name logic is incorrect	Recheck merge nodes, ensure file names include extensions
Duplicate PR created	Condition node not properly checking branch	Update condition to check existing PR or use unique branch name
Figma API returns 403/401	Invalid or expired Figma token	Regenerate token and update n8n credentials
GitHub file upload fails	Wrong path or binary input mismatch	Ensure correct folder structure (`drawable-mdpi`, etc.) and valid binary
Assets missing certain resolutions	Not all resolutions exported in Figma	Export all densities in Figma, or fallback to default

Need Help?

If you’d like help setting up, customizing or expanding this flow, feel free to reach out to our n8n automation team at WeblineIndia!

We can help you:

Fine-tune Figma queries
Improve file renaming rules
Integrate Slack / CI pipelines
Add support for other platforms (iOS/Web)

Happy automating!

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Merge

Type / Role: n8n-nodes-base.merge - merge
Config choices: Version 3.2

Block 2 - Download Each Image from the Figma Export URL

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 3 - get figma Url

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 4 - Merge1

Type / Role: n8n-nodes-base.merge - merge
Config choices: Version 3.2

Block 5 - If

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.2

Block 6 - Get Figma Export URL

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 7 - Execute workflow

Type / Role: n8n-nodes-base.manualTrigger - manualTrigger
Config choices: Version 1

Block 8 - Find Icons & Buttons

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 9 - Predefine drawable folders

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 10 - Filter nullable url of nodes

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 11 - Edit File names

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 12 - Prepare Pull Request

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 13 - Sticky Note

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 14 - Sticky Note1

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

3. Summary Table

Workflow	Sync Android drawable assets from Figma to GitHub via PR (multi-density PNG)
Complexity	intermediate
Nodes	14
Categories	File Management, Multimodal AI
Author	WeblineIndia
Published	01 Sept 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/8112/8112.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source File Management workflows Multimodal AI workflows

Frequently asked questions

What does Sync Android drawable assets from Figma to GitHub via PR (multi-density PNG) do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your File Management, Multimodal AI use case.

WeblineIndia

216 workflows

Nodes

n8n-nodes-base.merge n8n-nodes-base.httprequest n8n-nodes-base.if n8n-nodes-base.manualtrigger n8n-nodes-base.code n8n-nodes-base.stickynote

Complexity

intermediate

Published 01 Sept 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/8112/8112.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Export WordPress data to a CSV file

## Quick Overview This workflow manually exports all records from a WordPress site, converts the returned JSON into a CSV file, and saves the CSV to disk on the n8n server. ## How it works 1. Starts when you manually click Execute in n8n. 2. Fetches all available items from your connected WordPress site via the WordPress API. 3. Converts the WordPress JSON response into a CSV file. 4. Writes the generated CSV to the n8n server as `data.csv`. ## Setup 1. Add WordPress API credentials in n8n (site URL, username, and an Application Password). 2. Choose the WordPress resource to export in the WordPress node and confirm the data shape matches what you want in the CSV. 3. Update the output file path/name in the file-writing step and ensure the target directory is writable on your n8n host (for example `/home/node/.n8n/data.csv`).

View

Aggregate shipment tracking statuses with FedEx, UPS and DHL

## Quick Overview This workflow runs every 15 minutes to fetch active shipments from an n8n Data Table, query FedEx, UPS, or DHL tracking APIs with circuit-breaker protection, normalize each response into a shared status schema, and upsert the latest status back into the same table. ## How it works 1. Runs every 15 minutes on a schedule. 2. Loads all rows from the n8n Data Table `shipment_tracking` and filters out shipments already marked as DELIVERED or RETURNED_TO_SENDER. 3. Routes each remaining shipment by `carrier` and marks unsupported carriers with a canonicalStatus of UNKNOWN. 4. For FedEx, UPS, and DHL shipments, checks a per-carrier circuit breaker and either calls the carrier’s tracking API or skips the call when the breaker is open. 5. Normalizes each carrier response (or skip) into a canonical status (for example PRE_TRANSIT, IN_TRANSIT, OUT_FOR_DELIVERY, DELIVERED, EXCEPTION, UNKNOWN) while updating the breaker state based on 429/5xx/network failures. 6. Merges all carrier results and upserts the latest fields back into the `shipment_tracking` Data Table using `trackingNumber` as the match key. ## Setup 1. Create the n8n Data Table named `shipment_tracking` with columns such as `trackingNumber`, `carrier`, `canonicalStatus`, `rawStatus`, `breakerState`, `httpStatus`, and `checkedAt`, and seed it with shipments (use lowercase carriers: `fedex`, `ups`, `dhl`). 2. Add OAuth2 credentials for the FedEx Track API and select them in the FedEx HTTP request step. 3. Add OAuth2 credentials for the UPS Track API and select them in the UPS HTTP request step. 4. Add DHL API authentication (as configured for the DHL request in this template) and select it in the DHL HTTP request step. 5. Activate the workflow so workflow static data persists between runs and the circuit breaker state is maintained.

View

Clean up watched Jellyfin media and completed torrents with Transmission

## Quick Overview This scheduled workflow cleans up watched media in Jellyfin and removes completed torrents from Transmission by calling both APIs, deleting played items in Jellyfin, refreshing the Jellyfin library, and deleting torrents (including local data) once they reach the completed status. ## How it works 1. Runs daily on a schedule at the configured hour. 2. Sets the Jellyfin base URL, Jellyfin user ID, and Transmission base URL used for subsequent API calls. 3. Fetches played Movies and Episodes from Jellyfin for the configured user, deletes each returned item, and triggers a Jellyfin library refresh. 4. Calls the Transmission RPC endpoint to retrieve the required X-Transmission-Session-Id, then re-requests the torrent list using that session header. 5. Splits the Transmission response into individual torrents, filters to those with status 6 (completed), and removes each matching torrent while also deleting its local data. ## Setup 1. Add Jellyfin HTTP Header Auth credentials (for example, an API key header) and fill in the Jellyfin server URL and target Jellyfin user ID in the Variables step. 2. Add Transmission Bearer Auth credentials and set your Transmission base URL in the Variables step. 3. Confirm your Transmission instance allows RPC access at `/transmission/rpc` and that your Jellyfin server exposes the `/Users/{userId}/Items`, `/Items/{id}`, and `/Library/Refresh` endpoints for the provided credentials.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Sync Android drawable assets from Figma to GitHub via PR (multi-density PNG)

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Sync Android drawable assets from Figma to GitHub via PR (multi‑density PNG)

Who’s it for

How it works

How to set up

Requirements

How to customize

Add‑ons

Use Case Examples

Common Troubleshooting

Need Help?

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Merge

Block 2 - Download Each Image from the Figma Export URL

Block 3 - get figma Url

Block 4 - Merge1

Block 5 - If

Block 6 - Get Figma Export URL

Block 7 - Execute workflow

Block 8 - Find Icons & Buttons

Block 9 - Predefine drawable folders

Block 10 - Filter nullable url of nodes

Block 11 - Edit File names

Block 12 - Prepare Pull Request

Block 13 - Sticky Note

Block 14 - Sticky Note1

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions