Skip to content

Conversation

@protoss70
Copy link
Contributor

@protoss70 protoss70 commented Oct 24, 2025

Implemented docs for the new Airtable integration. Wrote detailed instructions on how to install, run an Actor and map the results.

I left there one TODO item since we dont have the Apify extension published I couldn't put there extension search result Apify so we need to improve it in the future. Ticket: #2042

@protoss70 protoss70 requested a review from drobnikj October 24, 2025 17:40
@protoss70 protoss70 requested a review from TC-MO as a code owner October 24, 2025 17:40
@protoss70 protoss70 added high priority Do this ASAP! This is for mission-critical work or work that blocks other teams in their work. product roadmap Issues synchronized to product roadmap. t-integrations Issues with this label are in the ownership of the integrations team. labels Oct 24, 2025
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR is being reviewed by Cursor Bugbot

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

Comment @cursor review or bugbot run to trigger another review on this PR

title: Airtable integration
description: Connect Apify with Airtable.
sidebar_label: Airtable
sidebar_position: 4
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Sidebar Position Conflict Between Files

The sidebar_position is set to 4, which conflicts with console_integration.md that also has sidebar_position: 4. Since both files are in the same directory and index.md should be the main page while console_integration.md is a sub-section, they should have different sidebar positions. The index.md should have a lower position number than console_integration.md (e.g., index.md: 4, console_integration.md: 5).

Fix in Cursor Fix in Web

@apify-service-account
Copy link

Preview for this PR was built for commit 136710c and is ready at https://pr-2041.preview.docs.apify.com!

@apify-service-account
Copy link

Preview for this PR was built for commit c9241ec and is ready at https://pr-2041.preview.docs.apify.com!

@apify-service-account
Copy link

Preview for this PR was built for commit 9b1441d and is ready at https://pr-2041.preview.docs.apify.com!

@protoss70 protoss70 requested review from valekjo and removed request for drobnikj October 27, 2025 13:47
@protoss70
Copy link
Contributor Author

protoss70 commented Oct 27, 2025

Adding @DaveHanns since @drobnikj is taking parental leave :)

@protoss70 protoss70 requested review from DaveHanns and removed request for valekjo October 27, 2025 13:51
Comment on lines 95 to 104
**Example Source**: crawl.depth <br/>
**Apify Field**:

```bash
{
crawl: {
depth: 3,
}
}
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is this supposed to be? What does it explain?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So the source crawl.depth is referring to the children field depth of crawl in the api result. If you check out the field preview image you can see on the right side fields with "."s in the name. I am not sure if this is very clear in the docs.

protoss70 and others added 2 commits October 28, 2025 16:41
Co-authored-by: Michał Olender <92638966+TC-MO@users.noreply.github.com>
@apify-service-account
Copy link

Preview for this PR was built for commit 2e917279 and is ready at https://pr-2041.preview.docs.apify.com!

@protoss70 protoss70 requested a review from TC-MO October 28, 2025 15:45
@apify-service-account
Copy link

Preview for this PR was built for commit d9312d1b and is ready at https://pr-2041.preview.docs.apify.com!

@apify-service-account
Copy link

Preview for this PR was built for commit d22deca9 and is ready at https://pr-2041.preview.docs.apify.com!

@apify-service-account
Copy link

Preview for this PR was built for commit 0eede6ce and is ready at https://pr-2041.preview.docs.apify.com!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

high priority Do this ASAP! This is for mission-critical work or work that blocks other teams in their work. product roadmap Issues synchronized to product roadmap. t-integrations Issues with this label are in the ownership of the integrations team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants