docs: add Albato integration page#2481
Conversation
Adds how-to documentation for the Albato integration with Apify, including setup steps, workflow examples, available triggers and actions, and 8 annotated screenshots. URL: https://docs.apify.com/platform/integrations/albato
marcel-rbro
left a comment
marcel-rbro
left a comment
There was a problem hiding this comment.
Hi, thanks for the PR.
Before this can merge, the page needs some changes to match our docs standards. A couple of things will fail CI as-is (em dashes throughout, and the blockquote formatting in the triggers/actions section produces markdownlint errors), plus some smaller style and terminology issues.
Useful references:
- CONTRIBUTING.md and the standards/ folder - especially writing-style.md, grammar-rules.md (no em dashes, use -), and terminology.md (Actor/task/dataset capitalization).
- If you're using an AI coding agent, this repo ships two skills that do most of this work: /doc-write for writing/editing to spec, and /review-docs for running the same review applied here.
- zapier.md is the closest existing page - worth modeling the triggers/actions section after it.
Ping me once it's updated and I'll take another look.
- Replace em dashes with hyphens (Microsoft.Dashes / Vale) - Restructure triggers and actions to use heading + blockquote format (matching zapier.md), fixes markdownlint errors - Apply Apify terminology: lowercase task/dataset/key-value store, capitalized Actor as proper noun - Sentence case in headings (Apify product names stay capitalized) - Add doc links for dataset and key-value store
check-frontmatter.sh requires 140-160 char range; previous version was 135. Reinstates 'automatically' to convey the workflow benefit.
- sidebar_position: 7 -> 7.0 (decimal format per content-standards.md) - Use contraction: 'you will need to' -> "you'll need to" - Replace 'kick off' with 'start' (avoid colloquialisms) - Rewrite Discord line to remove 'our' and first-person 'us' per writing-style.md: 'feel free to reach out to us on our X' -> 'join the X'
|
Hi @marcel-rbro ! Thanks for the detailed feedback. I’ve made the requested adjustments. Please let me know if anything else needs to be updated. |
|
GH api and inline comments just refuse to work today. I'll post the comments here for now. I can convert them to line-level comments later whenever GH stops acting out. Line 5 — sidebar_position: 7.0 ▎ Use integers -> 7 Line 11 — intro paragraph ▎ Could you start with a one-liner introducing Albato itself? Something like "Albato is a no-code automation platform...". Most readers landing here Line 21 — start of prerequisites list ▎ Small thing - could you pull this out into its own ## Prerequisites section? That's the pattern most of our other integration pages use now. Line 64 — start of "Build a workflow with an Apify trigger" ▎ These are nicely written. One thought - all the screenshots are on the connection setup. A single screenshot of the trigger config inside one of the Line 84 — last paragraph of "Build a workflow with an Apify action" ▎ Worth adding a short note about long-running runs somewhere on this page. Apify Actors often run for many minutes, which doesn't play well with sync Line 100 — Run Actor blockquote ▎ The descriptions here are a bit thin. Could you flesh out Run Actor and Run task - mainly whether they wait for the run to finish or not? That's the Line 142 — ## Resources heading ▎ Could you add a short ## Troubleshooting section before this? Doesn't need to be long - just the usual suspects (token issues, Actor not showing up |
- sidebar_position: 7.0 -> 7 (use integers, per maintainer comment) - Open with a one-liner introducing Albato, since most readers landing here from search won't know the platform - Move prerequisites into its own ## Prerequisites section, matching the pattern used on other integration pages - Add 'Handling long-running Actors' subsection explaining the async pattern (start the run, use Finished Actor Run trigger to continue) - Apify Actors often run for many minutes - Flesh out Run Actor / Run task descriptions: clarify that they return immediately and pair with Finished Actor/task Run for results, which is the question users actually have - Add ## Troubleshooting section covering invalid tokens, Actors not in dropdown, sync timeouts, and empty datasets
Adds screenshots for both example workflows the reviewer asked for: - Step 1 trigger setup (Finished actor run) - Step 2 action setup (Get dataset) - Step 3 Google Sheets action (Create/update a row) - Final canvas of the three-step trigger-based workflow - Final canvas of the action-based workflow (HubSpot -> Run Actor) Also corrects the Google Sheets action name from 'Add Row' to 'Create/update a row' to match the actual Albato UI label.
Original screenshots in 'Connect Apify with Albato' are 624px wide. The 5 new workflow screenshots were 2000px, rendering ~3x larger. Resized to 624px width preserving aspect ratio for visual consistency across the page.
All Albato connection-setup screenshots are 624x344. The 5 new workflow screenshots had varying heights (254, 336, 344, 351, 426), which caused visible inconsistency on the rendered page. Resized each new screenshot to fit a 624x344 canvas while preserving aspect ratio (no distortion), centering the content with white padding where the original aspect differed. All images on the page now render at identical dimensions.
Reverts the 624x344 padded version. All 5 new screenshots are now 624 pixels wide (matching the originals in the connection-setup section) with heights scaled proportionally to each screenshot's natural aspect ratio - no white padding, no distortion.
|
Hi @marcel-rbro ! I’ve made the new requested adjustments. Please let me know if anything else needs to be updated. |
3 participants
Summary
/integrations/albatoTest plan
https://docs.apify.com/platform/integrations/albatoThirdPartyDisclaimercomponent renders?? Generated with Claude Code